Compatibility Matrix

The table records the stack releases documented in this edition. Umbrella versions and docs editions identify a combination of independently released stacks. Stack, chart and image versions do not need matching version numbers.

Selected stack releases

Compatibility and maintenance policy

Later patch or minor releases can be used when their stack compatibility and migration requirements are satisfied. “Or later” does not mean any later major release, same-numbered stack versions, or an arbitrary mix of releases.

• Each stack maintains its latest minor train and the preceding train (N and N-1). Older trains receive no further patches.
• Patch upgrades within a train are supported. Cross-stack compatibility declarations still govern which stack trains can run together.
• When crossing more than one train, upgrade through the latest patch of each intermediate train. Complete its migration and upgrade prerequisites before continuing.

A product manifest fixes the stack releases and artifacts shipped in one umbrella archive. That selection does not replace the stack compatibility policy with an “only these versions are supported” restriction. A compatible range does not change the contents of an existing archive.

Follow the 1.0.4 upgrade notes for the docs edition 1.0.2 baseline and required upgrade order. Use Consume an NVCF release for package downloads.

For the separate 1.1 upgrade path, see its cross-stack upgrade order. That contract applies to its listed starting releases; it does not change the exact 1.0.4 selection above.