chore(release): stage v2.6.0 metadata with honest support boundary #105
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/v260-metadata"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The v2.6.0 carrier and local official-client slices are merged, but the source metadata still says v2.5.1 and the public support matrix overstates historical production status. Retargeting the version without refreshing release-tag tests would break their validation.
Approach
Validation
cargo test --locked --workspace(206 passed, 4 ignored),cargo fmt --all -- --check,cargo clippy --locked --workspace --all-targets -- -D warnings, focused SDK-domain test,bash scripts/test-container-image-tag.sh,bash scripts/test-v240-axis-b-ivnp-smoke.sh, andgit diff --checkpassed locally. Await required CI on this exact head before merge.Scope / risk
This PR is staged metadata and documentation only. It does not establish a public Axis B pass, publish an image, tag, or deploy. The release latch stays fail-closed.