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
22 releases 88 tags
  • v2.6.0+rs.1 ec663de48a

    v2.6.0+rs.1
    All checks were successful
    Rust CI / Format, lint, and test (push) Successful in 5m38s
    Details
    Rust CI / Build and start linux/arm64 image (no push) (push) Successful in 20s
    Details
    Build and publish container image / Build linux/arm64 image (push) Successful in 6m25s
    Details
    Stable

    ada released this 2026-10-08 17:18:41 +00:00 | 9 commits to master since this release

    Rust relay compatibility release for upstream portal-tunnel v2.6.0.

    Highlights:

    • Retargets the compatibility baseline to upstream v2.6.0 (protocol 10), including the WebSocket carrier used by the browser/WASM client.
    • Serves /sdk/certificate-chain with CORS headers so browser/WASM clients can complete keyless registration (PR #109).
    • Scopes the release gate to the deployed runtime: overlay (IVNP) is shipped but not enabled on this deployment, so the public gate covers direct paths and verifies that --overlay requests fall back to direct and that no overlay endpoint is advertised (PR #107).

    Compatibility:

    • Official v2.6.0 and v2.5.0 clients: native direct HTTP and browser/WASM verified against the deployed image.
    • Official v2.6.1 clients do not register yet (relay did not return canonical hostname). This is not a regression: the previous production release behaves the same way. Tracked for the next retarget (PR #108 non-regression rule).

    Verification:

    • PR CI and the linux/arm64 image workflow passed for the release revision.
    • The exact v2.6.0+rs.1-dev.4 image passed the public live gate on the production relay: v2.6.0/v2.5.0 native nonce round-trips, --overlay direct fallback, browser/WASM nonce round-trip with checksum-pinned assets, relay-served WASM asset checksums, release/health, and no overlay advertisement.
    • Earlier dev candidates were rolled back automatically: dev.2 exposed the missing CORS header; dev.3 failed only because post-swap re-registration from co-located clients exhausted the shared pre-auth budget, which the live procedure now waits out before gating.
    • Production reports v2.6.0+rs.1 / protocol 10; all long-running official expose services were upgraded to v2.6.0 and passed public endpoint checks.

    Image: code.rly.best/gofix/portal-tunnel-rs:v2.6.0-rs.1
    Digest: sha256:31839d1a55c07e6ee33e6dc41eaf4b53ca2cdf4c576a2e522a51940dba27a7c9
    Revision: ec663de48a
    Upstream: https://github.com/gosuda/portal-tunnel/releases/tag/v2.6.0

    Downloads