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
16 releases 45 tags
  • v2.3.8+rs.1 3217a6a3e1

    v2.3.8+rs.1
    All checks were successful
    Rust CI / Format, lint, and test (push) Successful in 1m33s
    Details
    Build and publish container image / Build linux/arm64 image (push) Successful in 4m56s
    Details
    Stable

    gofix released this 2026-08-25 14:11:29 +00:00 | 3 commits to master since this release

    Rust relay release retargeted to upstream portal-tunnel v2.3.8 (f73614e2fd51481e62fd7cbcb928d349e45eb6f0).

    Changes:

    • Isolates unverified discovery candidates until direct authoritative target verification, caps candidates per signing identity, and evicts candidates before verified relays.
    • Shares the upstream-compatible per-source announce budget across discovery announces and hop-route POSTs.
    • Matches the v2.3.8 /sdk/domain ENS provider response shape and explicitly rejects the unsupported embedded authoritative DNS provider.
    • Retargets version metadata, compatibility documentation, fixtures, and official-client/API/JWT smoke defaults to v2.3.8 and Go 1.27.
    • Preserves tunnel/discovery protocol 8 and legacy v2.1.8/v2.1.9 hop-route signature acceptance.

    Artifacts:

    • Git tag: v2.3.8+rs.1
    • OCI image: code.rly.best/gofix/portal-tunnel-rs:v2.3.8-rs.1
    • OCI digest: sha256:a57b2eaf6c84614927f34be4b67a0715f9570cd4d1c23bf4c16607199e01e171
    • Revision: 3217a6a3e179a305b3c29ec2c9a28e932cb081cc
    • Verified dev image: v2.3.8-rs.1-dev.1 at sha256:60f8e7fac24b95bfedd556c04e16d4f690c3f849837bda435b8f0f3d20574b82

    Verification:

    • PR #89 CI run #154 and target-branch CI run #155 passed; dev image run #156 and production image run #157 passed.
    • Formatting, Clippy with warnings denied, 151 tests (3 capability-dependent ignored), Go/Rust API shape, Go-issued JWT, and official v2.3.8 HTTP/lifecycle/TCP/UDP smokes passed.
    • Relay-host registry realm resolution/reachability and authenticated manifest lookup passed before dev tagging.
    • Dev and production direct official-client HTTP gates passed.
    • Canonical protocol-8 Axis B three-hop gates passed with rly.best as the middle relay for both dev and production wire releases.
    • The checksum-verified official arm64 v2.3.8 CLI was installed; all eight production expose services, including the code tunnel, were restarted/reattached and verified.
    • Local/public relay health and release surfaces passed. A first production switch was automatically rolled back on recovery-metadata validation; the metadata was corrected, the same immutable image redeployed, and all final gates passed.
    • Verification fixtures and stopped backup containers were cleaned; no certificate/identity volumes were removed.
    Downloads