gofix/portal-tunnel-rs
1
0
Fork 0
Code Issues Pull requests Projects Releases 11 Packages 1 Wiki Activity Actions

chore: retarget upstream portal-tunnel v2.3.2 #80

Merged
gofix merged 1 commit from codex/release-v2.3.2-20260606T133940Z-v2.3.2 into master 2026-06-06 14:00:44 +00:00
Conversation 1 Commits 1 Files changed 13 +44 -43
gofix commented 2026-06-06 13:46:15 +00:00
Owner
Copy link

Summary

  • Retarget Rust relay compatibility metadata from upstream portal-tunnel v2.3.1 to v2.3.2.
  • Upstream v2.3.2 diff is limited to x402/payment-app/frontend presentation, x402 facilitator dependency and Sui gRPC endpoint handling, plus the upstream release manifest version.
  • No Rust relay protocol logic change is needed because relay-local x402 facilitator endpoints remain explicitly unsupported and fail startup when enabled.

Upstream inspection

Checks

  • cargo fmt --check passed locally.
  • git diff --check passed locally.
  • Forgejo PR CI run #123 passed: Rust CI format, tests, clippy.
  • Linux/build-host focused test passed: cargo test --locked -p portal-relay sdk_domain_response_matches_fixture.
  • Linux/build-host full scripts/dev-rust-ci.sh completed format, tests, and clippy successfully; its first wrapper command had a post-check temporary cleanup permission error from root-owned Docker test files, then cleanup was handled with Docker-owned cleanup.
  • Interop smokes passed on linux/arm64 build host: official v2.3.2 HTTP, TCP, UDP, lifecycle; Go-issued JWT compatibility; Go v2.3.2 relay vs Rust relay API/discovery shape comparison.
  • Direct macOS cargo test is not applicable: Linux-only netlink-sys dependency does not compile on macOS.

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 from upstream portal-tunnel v2.3.1 to v2.3.2. - Upstream v2.3.2 diff is limited to x402/payment-app/frontend presentation, x402 facilitator dependency and Sui gRPC endpoint handling, plus the upstream release manifest version. - No Rust relay protocol logic change is needed because relay-local x402 facilitator endpoints remain explicitly unsupported and fail startup when enabled. ## Upstream inspection - Release: https://github.com/gosuda/portal-tunnel/releases/tag/v2.3.2 - Baseline: v2.3.1 `594497de27f79c4ab856f284c542f767ce498bb7` - Target: v2.3.2 `446820701972aa2053d477eb455bb09aee421ecd` - Protocol versions remain tunnel `8`, discovery `8`; Rust SDK/discovery constants stay unchanged. ## Checks - `cargo fmt --check` passed locally. - `git diff --check` passed locally. - Forgejo PR CI run #123 passed: Rust CI format, tests, clippy. - Linux/build-host focused test passed: `cargo test --locked -p portal-relay sdk_domain_response_matches_fixture`. - Linux/build-host full `scripts/dev-rust-ci.sh` completed format, tests, and clippy successfully; its first wrapper command had a post-check temporary cleanup permission error from root-owned Docker test files, then cleanup was handled with Docker-owned cleanup. - Interop smokes passed on linux/arm64 build host: official v2.3.2 HTTP, TCP, UDP, lifecycle; Go-issued JWT compatibility; Go v2.3.2 relay vs Rust relay API/discovery shape comparison. - Direct macOS `cargo test` is not applicable: Linux-only `netlink-sys` dependency does not compile on macOS. ## 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.2
All checks were successful
Rust CI / Format, lint, and test (pull_request) Successful in 3m45s
Details
7e567c45b0
gofix merged commit f9a590a705 into master 2026-06-06 14:00:44 +00:00
gofix commented 2026-06-06 14:19:37 +00:00
Author
Owner
Copy link

Post-merge release verification stopped before production promotion.

  • Dev tag/image verified: v2.3.2+rs.1-dev.1 / v2.3.2-rs.1-dev.1.
  • Relay was switched to the dev image and local/public /sdk/domain reported v2.3.2+rs.1-dev.1.
  • Official upstream v2.3.2 direct HTTP smoke passed.
  • Representative official-client multi-hop smokes registered routes but failed to return the expected backend payload through the public endpoint.
  • Per release policy, the relay was rolled back to the previous v2.3.1-rs.1 container; local/public /sdk/domain now report v2.3.1+rs.1.
  • Existing production expose services were restarted once after rollback and public endpoint probes recovered.

Production tag v2.3.2+rs.1 was not created, no production image was promoted, and official production client binaries were not upgraded.

Post-merge release verification stopped before production promotion. - Dev tag/image verified: `v2.3.2+rs.1-dev.1` / `v2.3.2-rs.1-dev.1`. - Relay was switched to the dev image and local/public `/sdk/domain` reported `v2.3.2+rs.1-dev.1`. - Official upstream v2.3.2 direct HTTP smoke passed. - Representative official-client multi-hop smokes registered routes but failed to return the expected backend payload through the public endpoint. - Per release policy, the relay was rolled back to the previous `v2.3.1-rs.1` container; local/public `/sdk/domain` now report `v2.3.1+rs.1`. - Existing production expose services were restarted once after rollback and public endpoint probes recovered. Production tag `v2.3.2+rs.1` was not created, no production image was promoted, and official production client binaries were not upgraded.
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!80
No description provided.