Platform Releases & Changelog
Track product updates, architectural migrations, breaking changes, and SDK releases across the Kontyra developer platform.
1. Release Cadence & Philosophy
Kontyra follows strict Semantic Versioning (SemVer 2.0). Breaking API changes are never introduced in minor or patch releases and are accompanied by an 18-month deprecation timeline with automated migration tooling.
Zero-downtime rolling updates verified against internal test suites
End-to-end sandbox builds, cryptographic ticket generation, and API test suites pass.
Rolled out to 5% of global edge traffic; monitors error rates, p99 latency, and WebSocket stability.
Promoted across all worldwide edge regions with instant documentation synchronization.
v2.0.0
Major ReleaseUnified Kontyra Console, OIDC Discovery & Apple Monochrome UI
- Kontyra Console Launch: Launched console.kontyra.name.ng for organization multi-tenancy, departmental teams, and RBAC roles.
- RFC 8414 OpenID Connect Discovery: Implemented standard metadata discovery at .well-known/openid-configuration.
- OAuth 2.0 Token Grant Endpoint: Added support for PKCE-secured authorization codes, refresh token rotation, and client credentials.
- Tamper-Resistant Audit Trail: Immutable security logging with actor IDs, IP tracking, and timestamp verification.
- Modern Next.js 16 Documentation: Upgraded docs.kontyra.name.ng to Next.js 16 App Router with pure Apple black-and-white minimalist design and interactive visual pipeline diagrams.
v1.2.0
Feature ReleaseDevOS Edge Deployments & VUX QR Ticketing
- Automated Edge Subdomains: Instant deployment previews mapped to
https://{project}-{user}.devos.kontyra.name.ng. - Official CLI Tooling: Released
@kontyra/devoswith interactive terminal TUI dashboard and headless flags. - VUX Cryptographic Check-in: Shipped in-browser door scanner with single-use atomic check-in enforcement.
v1.0.0
Initial LaunchInitial Launch of Kontyra Identity & REST Gateway
- Universal Single Sign-On: Unified authentication across developer accounts.
- API Gateway (/v1): Central entry point with CORS, rate limiting, and Bearer token validation.
5. Deprecation & Upgrade Policy
When an API field or endpoint is marked deprecated, it remains functional and receives security patches for at least 18 months. Deprecation warnings are surfaced in response headers via the standard Sunset and Deprecation HTTP headers.