gofix/portal-tunnel-rs
Watch
1
0
Fork
You've already forked portal-tunnel-rs
 0
Code Issues Pull requests Projects Releases 22 Packages 1 Wiki Activity Actions

docs: mark v2.6.1+rs.1 as the current production release #112

Merged
gofix merged 1 commit from docs/post-release-v2.6.1 into master 2026-10-09 12:30:22 +00:00
Conversation 0 Commits 1 Files changed 3 +29 -35
ada commented 2026-10-09 12:26:31 +00:00
Collaborator

Problem

README.md and docs/unsupported-features.md still describe v2.6.1 as a staged, unverified target with production on v2.5.0+rs.1. v2.6.0+rs.1 and v2.6.1+rs.1 have since been promoted after passing the public live gate (see their release notes), so the default branch understates the current state.

Change

  • README: current production v2.6.1+rs.1, latest pointer, tag list adds v2.6.0+rs.1 / v2.6.1+rs.1, drops the "no v2.6.0 tag" note.
  • Support matrix: release-status section now records the exact-image public live-gate evidence (v2.6.1/v2.6.0/v2.5.0 native, v2.6.1 browser/WASM WebSocket/yamux, keyless TLS, --overlay direct fallback, no overlay advertisement). Overlay remains shipped but not live-verified.
  • RELEASE.md step 8: updating these status documents is part of publishing a release, so this drift does not recur.

Docs only; no code or workflow changes.

## Problem `README.md` and `docs/unsupported-features.md` still describe v2.6.1 as a staged, unverified target with production on `v2.5.0+rs.1`. `v2.6.0+rs.1` and `v2.6.1+rs.1` have since been promoted after passing the public live gate (see their release notes), so the default branch understates the current state. ## Change - README: current production `v2.6.1+rs.1`, `latest` pointer, tag list adds `v2.6.0+rs.1` / `v2.6.1+rs.1`, drops the "no v2.6.0 tag" note. - Support matrix: release-status section now records the exact-image public live-gate evidence (v2.6.1/v2.6.0/v2.5.0 native, v2.6.1 browser/WASM WebSocket/yamux, keyless TLS, `--overlay` direct fallback, no overlay advertisement). Overlay remains shipped but not live-verified. - RELEASE.md step 8: updating these status documents is part of publishing a release, so this drift does not recur. Docs only; no code or workflow changes.
docs: mark v2.6.1+rs.1 as the current production release
All checks were successful
Rust CI / Format, lint, and test (pull_request) Successful in 3m11s
Details
Rust CI / Build and start linux/arm64 image (no push) (pull_request) Successful in 10s
Details
e473c1b3c0 
README and the support matrix still described v2.6.1 as a staged target with production on v2.5.0+rs.1, although v2.6.0+rs.1 and v2.6.1+rs.1 were promoted after passing the public live gate. Record the promoted tags and the live-gate evidence, and make the status-document update part of release step 8.
gofix merged commit d6f1b5dc2b into master 2026-10-09 12:30:22 +00:00
gofix deleted branch docs/post-release-v2.6.1 2026-10-09 12:30:22 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!112
No description provided.