Skip to content

@polymorph/iroh 0.5.1 - #99

Merged
lannbot merged 1 commit into
mainfrom
iroh-0.5.1
Aug 23, 2026
Merged

@polymorph/iroh 0.5.1#99
lannbot merged 1 commit into
mainfrom
iroh-0.5.1

Conversation

@lannbot

@lannbot lannbot commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Patch release bump: host-polyengine/deno.json version 0.5.0 → 0.5.1.

Content since v0.5.0 is the relay-robustness line — #91 (home-relay failure is a redial, not endpoint death), #95 (every relay dial carries a deadline), #97 (quiet relay wires are pinged; unanswered pings retire the connection) — plus the release plumbing (#92, #94). No WIT change and no JS-surface change (harness.ts/mod.ts/types.ts untouched since v0.5.0); the published @polyengine/runtime floor moved to ^0.5.1 in #95 (A23: dial timeouts drop in-flight import futures; polyengine#239), which stays inside the 0.5 line — patch-honest under the caret regime.

After merge: dispatch jsr-publish, which publishes JSR 0.5.1 and creates the v0.5.1 release; release-assets attaches iroh_endpoint.wasm + SHA256SUMS on publish.

Gates: just build-components + deno publish --dry-run clean locally; full just ci here.

Automerge is armed.

Patch release carrying the relay-robustness line landed since 0.5.0:
home-relay failure is a redial rather than endpoint death (#91), every
relay dial carries a deadline (#95), and quiet relay wires are pinged
with unanswered pings retiring the connection (#97). No WIT or JS
surface change; the published @polyengine/runtime floor is already
^0.5.1 (A23 prompt-discard of dropped import futures, polyengine#239).

Gates: build-components + deno publish --dry-run clean; full CI on the
PR.
@lannbot
lannbot enabled auto-merge August 23, 2026 23:28
@lannbot
lannbot merged commit 739d865 into main Aug 23, 2026
1 check passed
@lannbot
lannbot deleted the iroh-0.5.1 branch August 23, 2026 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants