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

chore: retarget upstream portal-tunnel v2.3.3 #81

Merged
gofix merged 1 commit from codex/release-v2.3.3-20260803T154033Z-v2.3.3 into master 2026-08-03 16:10:12 +00:00
Conversation 1 Commits 1 Files changed 13 +45 -44
gofix commented 2026-08-03 16:08:33 +00:00
Owner
Copy link

Summary

  • Retarget Rust relay compatibility metadata and official-client harnesses from upstream portal-tunnel v2.3.2 to v2.3.3.
  • Upstream v2.3.3 retains tunnel/discovery protocol version 8. Relay-server changes are behavior-preserving policy refactors; automatic multi-hop recovery changes are client-side, and Casper wCSPR x402 remains explicitly unsupported by this relay port.
  • Fix the current Rust toolchain's for_kv_map lint with an equivalent keys-only iteration and prevent the JWT interop harness from writing its generated test token to human-readable logs.

Upstream inspection

Checks

  • cargo fmt --check, git diff --check, and shell syntax checks passed.
  • Linux/build-host scripts/dev-rust-ci.sh passed: 137 tests passed, 3 capability-dependent tests ignored, clippy clean.
  • linux/arm64 candidate image build and runtime-state smoke passed.
  • Official v2.3.3 client HTTP, lifecycle/renew/unregister, raw TCP, and UDP smokes passed with release-asset sha256 verification.
  • Go-issued JWT compatibility and Go v2.3.3 relay vs Rust relay API/discovery shape comparison passed.
  • Direct macOS tests are not applicable because the relay depends on Linux Netlink; authoritative checks ran on the approved Linux build host.

Release audit trail

  • Dev counter trail: pending.
  • Tagged dev deploy image: pending.
  • Live verification: pending.
  • Production release tag/image: pending.
  • Release note link: pending.
## Summary - Retarget Rust relay compatibility metadata and official-client harnesses from upstream portal-tunnel v2.3.2 to v2.3.3. - Upstream v2.3.3 retains tunnel/discovery protocol version 8. Relay-server changes are behavior-preserving policy refactors; automatic multi-hop recovery changes are client-side, and Casper wCSPR x402 remains explicitly unsupported by this relay port. - Fix the current Rust toolchain's `for_kv_map` lint with an equivalent keys-only iteration and prevent the JWT interop harness from writing its generated test token to human-readable logs. ## Upstream inspection - Release: https://github.com/gosuda/portal-tunnel/releases/tag/v2.3.3 - Baseline: v2.3.2 `446820701972aa2053d477eb455bb09aee421ecd` - Target: v2.3.3 `7b5fbc31b6011423ff8f386651ecf631f2fdbd38` - Protocol versions remain tunnel `8`, discovery `8`; Rust SDK/discovery constants stay unchanged. ## Checks - `cargo fmt --check`, `git diff --check`, and shell syntax checks passed. - Linux/build-host `scripts/dev-rust-ci.sh` passed: 137 tests passed, 3 capability-dependent tests ignored, clippy clean. - linux/arm64 candidate image build and runtime-state smoke passed. - Official v2.3.3 client HTTP, lifecycle/renew/unregister, raw TCP, and UDP smokes passed with release-asset sha256 verification. - Go-issued JWT compatibility and Go v2.3.3 relay vs Rust relay API/discovery shape comparison passed. - Direct macOS tests are not applicable because the relay depends on Linux Netlink; authoritative checks ran on the approved Linux build host. ## Release audit trail - Dev counter trail: pending. - Tagged dev deploy image: pending. - Live verification: pending. - Production release tag/image: pending. - Release note link: pending.
chore: retarget upstream portal-tunnel v2.3.3
All checks were successful
Rust CI / Format, lint, and test (pull_request) Successful in 1m25s
Details
5d1188028b
gofix merged commit ae2af1d7e7 into master 2026-08-03 16:10:12 +00:00
gofix commented 2026-08-03 16:42:39 +00:00
Author
Owner
Copy link

Release verification trail:

  • v2.3.3+rs.1-dev.1: tag workflow failed before build/push when the public registry preflight returned EOF; counter consumed.
  • Recovery PR #82 changed CI publishing to the authenticated Tailscale registry endpoint and made latest production-only.
  • v2.3.3+rs.1-dev.2: tag workflow #132 passed; OCI v2.3.3-rs.1-dev.2 published at sha256:b9f5c4c89aa348a2913c8cea197909a88d34ad8e7b295c1e25ed72cb87dc8c9d.
  • Dev relay local/public health and official v2.3.3 direct HTTP passed; all inventoried production official clients were upgraded and restarted.
  • Required explicit multi-hop verification failed because the configured exit relay returned repeated HTTP 502 compatibility responses before payload verification.
  • Immediate rollback completed: relay and official clients restored to v2.3.1, all inventoried expose services restarted and public endpoints verified.
  • No production tag or production image was created.
Release verification trail: - `v2.3.3+rs.1-dev.1`: tag workflow failed before build/push when the public registry preflight returned EOF; counter consumed. - Recovery PR #82 changed CI publishing to the authenticated Tailscale registry endpoint and made `latest` production-only. - `v2.3.3+rs.1-dev.2`: tag workflow #132 passed; OCI `v2.3.3-rs.1-dev.2` published at `sha256:b9f5c4c89aa348a2913c8cea197909a88d34ad8e7b295c1e25ed72cb87dc8c9d`. - Dev relay local/public health and official v2.3.3 direct HTTP passed; all inventoried production official clients were upgraded and restarted. - Required explicit multi-hop verification failed because the configured exit relay returned repeated HTTP 502 compatibility responses before payload verification. - Immediate rollback completed: relay and official clients restored to v2.3.1, all inventoried expose services restarted and public endpoints verified. - No production tag or production image was created.
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!81
No description provided.