chore: retarget upstream portal-tunnel v2.3.0 #78

Merged

gofix merged 1 commit from codex/release-v2.3.0-20260601T053029Z-v2.3.0 into master 2026-06-01 06:00:42 +00:00

Conversation 0 Commits 1 Files changed 21 +178 -78

gofix commented 2026-06-01 05:58:41 +00:00

Owner

Copy link

Summary

Retargeted the Rust relay compatibility baseline to upstream gosuda/portal-tunnel v2.3.0.

Upstream release notes:

• nginx cleanup (#56)
• relay api routing (#57)

Relay-scope changes:

• Bumped workspace/reported upstream version to 2.3.0 and tunnel/discovery protocol to 8.
• Added upstream v2.3.0 /api/* relay API aliases while retaining legacy operator paths.
• Matched the v2.3.0 official client /sdk/connect raw-upgrade reverse-session handshake, while keeping the older 200/keep-alive response for legacy callers.
• Refreshed fixtures, compatibility docs, and release smoke defaults for v2.3.0.

Checks

• cargo fmt --check
• git diff --check
• scripts/dev-rust-ci.sh
• focused Linux tests for SDK domain fixture, /api/healthz, installer path injection, and /sdk/connect handshake
• scripts/v218-api-shape-compare.sh
• scripts/v218-jwt-verify-compat.sh
• scripts/v218-release-http-smoke.sh (rerun with isolated ports after a fixed-port collision)
• scripts/v218-release-lifecycle-smoke.sh (isolated ports)
• scripts/v218-release-tcp-smoke.sh (isolated ports)
• scripts/v218-release-udp-smoke.sh (isolated ports)
• scripts/track0-runtime-smoke.sh (isolated ports)
• Forgejo Rust CI on PR and post-merge master
• dev tag image workflow and registry tag verification
• live dev relay health, production client rollout, endpoint checks, direct HTTP smoke, and multi-hop smoke
• production tag image workflow and registry tag verification
• live production relay health, service restart/reattach, endpoint checks, direct HTTP smoke, and multi-hop smoke

Release Audit Trail

• Merge commit: b79f00bf750a68dfd773125086b7ff237681604a
• Tagged dev deploy: v2.3.0+rs.1-dev.1
• Dev image: code.rly.best/gofix/portal-tunnel-rs:v2.3.0-rs.1-dev.1
• Dev image digest: sha256:cbd88db5d07fb228ae0d58795b98adeba389e1b4b595ccd29cc5259448ddee37
• Production tag: v2.3.0+rs.1
• Production image: code.rly.best/gofix/portal-tunnel-rs:v2.3.0-rs.1
• Production image digest: sha256:fea2d4a06083baf2fc4d39ad6f4f097c5f25b9e972b26bde43c9cbb6e6b5b557
• Release note: https://code.rly.best/gofix/portal-tunnel-rs/releases/tag/v2.3.0+rs.1

Deployment Note

The production relay and long-running official portal CLI clients are now on v2.3.0. Production exposed services were restarted/re-attached after relay replacement. The standing multihop fixture service definitions still reference a protocol-7 discovery chain, so final multi-hop validation used a temporary protocol-8 live chain with the upgraded relay in the hop path.

## Summary Retargeted the Rust relay compatibility baseline to upstream `gosuda/portal-tunnel` `v2.3.0`. Upstream release notes: - nginx cleanup (#56) - relay api routing (#57) Relay-scope changes: - Bumped workspace/reported upstream version to `2.3.0` and tunnel/discovery protocol to `8`. - Added upstream v2.3.0 `/api/*` relay API aliases while retaining legacy operator paths. - Matched the v2.3.0 official client `/sdk/connect` raw-upgrade reverse-session handshake, while keeping the older 200/keep-alive response for legacy callers. - Refreshed fixtures, compatibility docs, and release smoke defaults for v2.3.0. ## Checks - `cargo fmt --check` - `git diff --check` - `scripts/dev-rust-ci.sh` - focused Linux tests for SDK domain fixture, `/api/healthz`, installer path injection, and `/sdk/connect` handshake - `scripts/v218-api-shape-compare.sh` - `scripts/v218-jwt-verify-compat.sh` - `scripts/v218-release-http-smoke.sh` (rerun with isolated ports after a fixed-port collision) - `scripts/v218-release-lifecycle-smoke.sh` (isolated ports) - `scripts/v218-release-tcp-smoke.sh` (isolated ports) - `scripts/v218-release-udp-smoke.sh` (isolated ports) - `scripts/track0-runtime-smoke.sh` (isolated ports) - Forgejo Rust CI on PR and post-merge `master` - dev tag image workflow and registry tag verification - live dev relay health, production client rollout, endpoint checks, direct HTTP smoke, and multi-hop smoke - production tag image workflow and registry tag verification - live production relay health, service restart/reattach, endpoint checks, direct HTTP smoke, and multi-hop smoke ## Release Audit Trail - Merge commit: `b79f00bf750a68dfd773125086b7ff237681604a` - Tagged dev deploy: `v2.3.0+rs.1-dev.1` - Dev image: `code.rly.best/gofix/portal-tunnel-rs:v2.3.0-rs.1-dev.1` - Dev image digest: `sha256:cbd88db5d07fb228ae0d58795b98adeba389e1b4b595ccd29cc5259448ddee37` - Production tag: `v2.3.0+rs.1` - Production image: `code.rly.best/gofix/portal-tunnel-rs:v2.3.0-rs.1` - Production image digest: `sha256:fea2d4a06083baf2fc4d39ad6f4f097c5f25b9e972b26bde43c9cbb6e6b5b557` - Release note: https://code.rly.best/gofix/portal-tunnel-rs/releases/tag/v2.3.0+rs.1 ## Deployment Note The production relay and long-running official `portal` CLI clients are now on v2.3.0. Production exposed services were restarted/re-attached after relay replacement. The standing multihop fixture service definitions still reference a protocol-7 discovery chain, so final multi-hop validation used a temporary protocol-8 live chain with the upgraded relay in the hop path.

gofix added 1 commit 2026-06-01 05:58:41 +00:00

chore: retarget upstream portal-tunnel v2.3.0 40747511bf

gofix merged commit b79f00bf75 into master 2026-06-01 06:00:42 +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

Subscribe

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!78

No description provided.