chore(release): stage v2.6.0 metadata with honest support boundary #105

Merged
ada merged 2 commits from feat/v260-metadata into master 2026-10-03 13:59:13 +00:00
Collaborator

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

  • Set workspace metadata to v2.6.0 while preserving tunnel protocol 10 / discovery protocol 9.
  • Document the local Darwin raw and Chrome/WASM mux evidence separately from the still-unpassed exact-image public Axis B authenticated IVNP/Go-control gate. Do not claim a tag, promotion, or deployment; production remains v2.5.0+rs.1.
  • Update version-dependent container-tag regression and API fixture; reject the stale v2.5.1 production tag.

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, and git diff --check passed 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.

## 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 - Set workspace metadata to v2.6.0 while preserving tunnel protocol 10 / discovery protocol 9. - Document the local Darwin raw and Chrome/WASM mux evidence separately from the still-unpassed exact-image public Axis B authenticated IVNP/Go-control gate. Do not claim a tag, promotion, or deployment; production remains v2.5.0+rs.1. - Update version-dependent container-tag regression and API fixture; reject the stale v2.5.1 production tag. ## 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`, and `git diff --check` passed 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.
test(release): retarget image tag and API fixtures to v2.6.0
All checks were successful
Rust CI / Format, lint, and test (pull_request) Successful in 3m35s
Rust CI / Build and start linux/arm64 image (no push) (pull_request) Successful in 59s
e367d6fa17
ada merged commit 70a1272d95 into master 2026-10-03 13:59:13 +00:00
ada deleted branch feat/v260-metadata 2026-10-03 13:59:13 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gofix/portal-tunnel-rs!105
No description provided.