gofix/portal-tunnel-rs
1
0
Fork 0
Code Issues Pull requests Projects Releases 11 Packages 1 Wiki Activity Actions
11 releases 27 tags
  • v2.2.2+rs.2 a96d959f33

    portal-tunnel-rs v2.2.2+rs.2
    All checks were successful
    Rust CI / Format, lint, and test (push) Successful in 53s
    Details
    Build and publish container image / Build linux/arm64 image (push) Successful in 3m13s
    Details
    Stable

    ada released this 2026-05-16 07:34:52 +00:00 | 9 commits to master since this release

    portal-tunnel-rs v2.2.2+rs.2

    Port patch on the v2.2.2 upstream target.

    Changed

    • Hardened relay HopMux outbound session handling under peer churn.
    • Finished outbound sessions are pruned before reuse/open, preventing stale peers from accumulating after disconnects.
    • Documented the development self-merge policy and the remaining multi-hop hardening scope.

    Compatibility

    • Upstream target: portal v2.2.2.
    • Protocol version: 7.
    • Interop window preserved: current documented v2.2.2 relay surface plus existing v2.1.8/v2.1.9 hop-route/multi-hop compatibility where documented.
    • Scope remains relay-server only; official upstream portal CLI remains the supported production client.

    Artifacts

    Validation

    • Dev gate:

      • Tagged dev deploy: v2.2.2+rs.2-dev.1
      • Dev image: code.rly.best/gofix/portal-tunnel-rs:v2.2.2-rs.2-dev.1
      • Deployed dev image reported release_version=v2.2.2+rs.2-dev.1 on /sdk/domain.
      • Official portal v2.2.2 direct HTTP smoke passed through rly.best.
      • Official portal v2.2.2 explicit multi-hop smoke passed with rly.best as the middle relay.
      • Production expose services were re-attached after the relay switch and public endpoints were verified.

    • Promotion:

      • Production image build succeeded and registry tag was verified.
      • Production relay reports protocol_version=7 and release_version=v2.2.2+rs.2.
      • https://rly.best/healthz and https://rly.best/sdk/domain passed.
      • Post-promotion direct and multi-hop official-client smokes passed.
      • Public production endpoints were re-attached and verified.

    Operational notes

    • Existing relay identity/certificate state was preserved across the dev and production container switches.
    • Previous relay containers were kept as timestamped rollback backups on the deployment host.
    • The object-storage endpoint returns HTTP 403 for unauthenticated root access; this was treated as a successful connectivity check rather than an app failure.
    Downloads