Release and versioning policy

This page belongs to the immutable 0.2.0 (Private Preview) documentation snapshot. The version selector changes the complete documentation set. Select Next (Private Preview) only when evaluating unreleased documentation.

Concepts, procedures, compatibility, Manager behavior, navigation, and search results remain scoped to the selected version. Always match documentation to the installed Nexo bundle before following operational guidance.

Every published Nexo release should provide:

• a unique, immutable version identifier;
• release date and maturity;
• supported upgrade paths;
• compatibility changes;
• new features and fixes;
• known issues;
• security-relevant notices where applicable;
• breaking changes and deprecations;
• rollback constraints.

Bundle and component versions

The customer-facing Nexo version identifies an immutable, tested release bundle. The bundle records independent component artifacts—including Manager, Operator, Proxy, and pipeline-step images—by repository, tag, and digest.

Customers should select and compare Nexo bundle versions. Component versions exist for diagnostics, release evidence, and compatibility preflight; they are not independent customer upgrade targets unless a component guide explicitly says otherwise.

See Nexo Manager versions for the Manager-specific contract.

Version numbers alone do not guarantee configuration or deployment compatibility. Follow the upgrade path published for the source and target versions.

Pre-release builds must be clearly labeled and should not be treated as production releases. A release is supported only according to the currently published support policy; this staged page does not define contractual support periods.