Public changelog
Shipped, dated, verifiable.
The public release record identifies the current version and access status. This page records selected changes and product milestones; a QA build or source change is not a customer release until the release record and acceptance evidence say so.
Releases
The machine-readable release record identifies the current application version and availability. See the access page.
Current release
v0.2.0
Windows · provided by request
v0.2.0September 18, 2026
Current Vendale release record
- Vendale branding across the desktop application and installers.
- Windows desktop client for customer conversations and connected workspace records.
- Human-reviewed AI assistance; customer replies remain drafts until a person approves them.
v0.1.5August 18, 2026
Login boundary made honest
- Any 401 from the email sign-in route is now normalized to a clear invalid-credentials message at the login boundary.
- Refresh tokens and protected-route behavior deliberately left untouched; the fix was scoped to one route, not the auth system.
- Verified with focused auth/client tests 22/22 and the full desktop suite 570/570 before release.
v0.1.4August 18, 2026
Error bodies stopped being thrown away
- Root cause: the native WebView can hide Content-Type on failures, so real JSON error details were being discarded and misread as a generic sign-in loop.
- Defensive JSON parsing restored for every non-success response; HTML or malformed bodies still fall back to safe HTTP status text.
- Regression coverage added for a JSON 401 with no Content-Type header, the exact shape that broke real users.
v0.1.3August 18, 2026
The misleading message fixed
- A wrong-password rejection was being classified as authentication_required, telling users they needed to sign in while they were already signing in.
- New invalid_credentials state points users at email, password, and workspace URL instead of a loop.
- Safe live probes confirmed requests were reaching the active backend; the failure was classification, not connectivity.
v0.1.2August 18, 2026
Registration repaired end to end
- A registration call was hitting the marketing host and receiving HTML instead of API JSON. A real client screenshot surfaced the issue at sign-up step 4.
- Desktop HTTP handling now rejects a non-JSON success response as a safe unexpected_api_response instead of exposing a parser error.
- Production build validation now refuses to build against a non-API origin, preventing this class of misrouting at build time.
Before the version numbers
The platform milestones.
PlatformSeptember–October 2026
The product and its release record take shape
- Vendale and Arche Axon product branding established across the application.
- The public release record tracks the current Windows version, availability, and supported platform details; the stable record remains invite-only with no public installer.
- Shared production hosting and a customer-managed production installation are still separate release-acceptance items; local and synthetic QA evidence is not customer deployment acceptance.
TrustAugust 2026
Messaging integration hardening in source
- Instagram identity, webhook signature, event schema, and duplicate-callback handling have source-level implementation work.
- Provider credentials, real customer traffic, and end-to-end acceptance for a customer release remain separate checks.
- Confirm supported channels and connection setup against the supplied release; code presence alone does not establish live availability.
ProductionJune 2026
Connected-workspace implementation groundwork
- The application separates demo behavior from API-connected workspace paths in source.
- Build and artifact checks are recorded for individual candidates; they are not equivalent to a signed, customer-accepted installer.
- The current public stable record remains the authority for customer availability and matching server/client compatibility.
Request access to the current release.
The current version and access status are available in the public release manifest.