-
portal-tunnel-rs v2.2.4+rs.1
Stablereleased this
2026-05-28 10:57:51 +00:00 | 6 commits to master since this releaseSummary
- Retarget the Rust relay compatibility baseline to upstream
gosuda/portal-tunnelv2.2.4. - Add the upstream
x402status object to/sdk/domainwithenabled=falsefor the Rust relay. - Add startup guards for unsupported relay-local X402 facilitator mode and unsupported Njalla ACME DNS configuration.
- Refresh fixtures, smoke defaults, docs, and version metadata for the
v2.2.4target.
Compatibility
- Upstream target:
v2.2.4. - Interop window remains documented in
docs/unsupported-features.md. - Relay reports
release_version=v2.2.4+rs.1on/sdk/domain. - Production image:
code.rly.best/gofix/portal-tunnel-rs:v2.2.4-rs.1. - Production manifest digest:
sha256:b05fa61d8772ecc7b50af54315b3743ae8e7953124c8b240e0a7dac3f4ea451a.
Validation
- PR #74 merged after required Forgejo Rust CI passed.
masterpush CI passed before tagging.- Tagged dev deploy:
v2.2.4+rs.1-dev.1/ imagev2.2.4-rs.1-dev.1. - Dev image workflow passed; manifest digest
sha256:137e55fb30fa41ad0f926662e263b1e0b43b1778a3b8798844c6019217ea00bf. - Dev relay live verification passed for local/public
/sdk/domain, officialv2.2.4direct HTTP, and officialv2.2.4explicit multi-hop withrly.bestas middle hop. - Production image workflow passed and the production relay was switched to
v2.2.4-rs.1. - Production direct HTTP and explicit multi-hop official-client smokes passed.
- Active long-running production
portal exposeclients were upgraded to official CLIv2.2.4, restarted, and theirrly.bestendpoints returned expected status codes. rust-relay-multihop-*validation fixtures were refreshed to official CLIv2.2.4and returned HTTP 200.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- Retarget the Rust relay compatibility baseline to upstream