Home / Documentation / Policies / Versioning

Versioning & Release Management

Standardized versioning protocols across all Aevum Zenth divisions, covering software APIs, internal tools, documentation, and enterprise-grade services.

📜 Enterprise Standard

This policy applies to all software products, microservices, SDKs, and internal platforms under the Aevum Zenth umbrella. Divisional overrides require CTO Office approval.

Semantic Versioning (SemVer 2.0.0)

All public-facing and internal software components adhere to Semantic Versioning 2.0.0. Versions follow the MAJOR.MINOR.PATCH format:

MAJOR - Incompatible API changes, breaking architectural shifts, or security overhauls
MINOR - Backward-compatible functionality additions or improvements
PATCH - Backward-compatible bug fixes and security patches

Pre-release and build metadata may be appended using -prerelease or +build suffixes where applicable.

JSON Example Manifest

{
  "name": "@aevum-zenth/core-sdk",
  "version": "4.2.1",
  "channel": "stable",
  "semver_compliant": true,
  "division": "Zenth Digital Systems",
  "release_date": "2026-01-15T00:00:00Z"
}

API Versioning Strategy

Aevum Zenth employs a dual-track API versioning approach to ensure maximum compatibility and clear migration paths:

1. URL Path Versioning (Primary)

Used for major architectural releases. Ensures clear separation of breaking changes.

HTTP

GET /api/v2/payments/transactions
POST /api/v3/data/export
GET  /api/v1/internal/metrics

2. Header Versioning (Fallback/Contract)

Used for minor schema changes, feature flags, and backward-compatible extensions within a major version.

HTTP Headers

Accept-Version: 2.14.3
X-API-Contract: v2
X-Feature-Flag: beta-predictive-analytics

⚠️ Migration Requirement

Any API reaching MAJOR v5 will require formal migration approval from the divisional architecture board. Sunset endpoints will return 410 Gone after the grace period.

Release Channels

Products are distributed through three standardized channels to manage risk and adoption velocity:

Channel	Status	Target Audience	Support SLA
Stable	Production-Ready	Enterprise clients, external partners, critical infrastructure	24/7 Priority
Beta	Feature Preview	Trusted partners, internal pilot teams, opt-in clients	Business Hours (9-5)
Internal/Alpha	Development Only	Divisional engineering, QA, architecture validation	Best Effort

Deprecation & End-of-Life (EOL)

Deprecations follow a strict 18-month lifecycle to ensure predictable transitions:

Announcement (Month 0-3) - Public notice, migration guides released, Deprecation: true header added to responses
Warning Phase (Month 4-12) - Rate limits reduced for legacy endpoints, console warnings issued, migration webinars scheduled
Sunset Phase (Month 13-18) - Read-only mode for legacy APIs, final data export windows, strict 410 Gone enforcement post-EOL

Emergency security deprecations may accelerate this timeline with 14-day notice following CVE disclosure protocols.

Support Lifecycle Matrix

Version Line	Release Date	Security Patches	Bug Fixes	Feature Updates	EOL Date
4.x (Current)	2026-01-15	✅ 24 Months	✅ 24 Months	✅ Active	2028-01-15
3.x (Legacy)	2024-06-01	⚠️ 6 Months	❌ Ended	❌ Ended	2026-06-01
2.x (Archived)	2022-11-10	❌ Ended	❌ Ended	❌ Ended	2024-11-10

Recent Changelog

Track major version releases and critical updates across the conglomerate's core platforms.

Version	Division	Type	Key Changes	Release
4.2.0	Zenth Digital Systems	Stable	Quantum-safe TLS 1.3 enforcement, unified auth gateway	Jan 15, 2026
4.1.5	Aevum Capital Group	Stable	Compliance engine v3, real-time AML screening pipeline	Jan 02, 2026
4.0.0-rc.2	Aevum Aerospace	Beta	Telemetry SDK rewrite, edge-compute data routing	Dec 10, 2025

🔗 Need assistance?

For migration support, version pinning requests, or divisional override approvals, contact the Platform Engineering Desk or open a ticket via the internal service portal.