polyengine 0.4.0 and the 0.4.0 sibling line; @polymorph/iroh 0.4.0 - #87
Merged
Conversation
Bump host-polyengine's published caret family to the ^0.4.0 line —
@polyengine/{runtime,translator,wasi} plus the sibling hosts
@polymorph/{webcrypto,websocket,webrtc-datachannels}, all released
today against polyengine v0.4.0 — and the relay-ws spike's exact
pins to match. Upstream's one breaking change (A19 err-result
brand-key rename) is internal to the engine; the stale WitError
class name in exam-polyengine's comment becomes ComponentException
(renamed upstream at 0.3.0).
Package version 0.4.0: the published ranges move minor lines, a
resolution-level break for consumers holding 0.3.0 pins.
Gates: exam-polyengine (7/7 scenarios; one runtime 0.4.0, no raw
URLs), just check, just ci — green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bump
host-polyengine's published caret family to the^0.4.0line —@polyengine/{runtime,translator,wasi}plus the sibling hosts@polymorph/{webcrypto,websocket,webrtc-datachannels}(all released today against polyengine v0.4.0) — and the relay-ws spike's exact pins to match.Upstream's one breaking change (the A19 err-result brand-key rename) is internal to the engine; the stale
WitErrorclass name inexam-polyengine's comment becomesComponentException(renamed upstream at 0.3.0). iroh-blobs' npm tree carries no polyengine-family pins (its imports route through the relay-ws deno config already bumped here).Package version 0.4.0: the published ranges move minor lines — a resolution-level break for consumers holding 0.3.0 pins.
Gates locally:
just exam-polyengine(7/7 scenarios; "one runtime (0.4.0), no raw URLs"),just check,just ci— all green.