Breaking changes and migrations
Proceed only when the selected manifest or an operator-provided release record identifies required migrations. Absence of that record is not evidence that no migration is required.
Versioned release records
Release identity and artifact details come from immutable publication manifests. Upgrade procedures remain separate from the release record.
Loading the selected release record…
Before upgrading production
Do not infer compatibility from a version number alone.
Known issues
The publication manifest currently carries artifact and provider support metadata, not a verified known-issues list. Obtain the release-specific issue record before rollout.
Supported upgrade path
Use the rolling-update workflow only for a path explicitly approved by the release operator. Follow the destructive migration warning in the operations guide for older standalone layouts.