polyengine 0.4.0; @polymorph/webrtc-datachannels 0.4.0 - #165
Merged
Conversation
Bump all three import maps (polyengine-impl, conformance driver, browser bundle) to the polyengine v0.4.0 release, and the runner core to @polymorph/test 0.2.1: the @jsr/polymorph__test npm tree plus the four component-test-* cargo revs and the conformance.yml action refs, all naming the one polymorph-test v0.2.1 release (9f9e4d5). Upstream's one breaking change (A19 err-result brand-key rename) is internal to the engine; wasmtime-impl's WitError alias is the WIT-generated error type, unrelated. The impl already recognizes values by @polyengine/protocol predicates. Package version 0.4.0: the published deno.json's @polyengine/runtime range moves to ^0.4.0, a resolution-level break for consumers holding 0.3.0 pins. Gates: just polyengine-check (pin gates + 13/13 impl tests + driver deno checks), cargo check --workspace. The conformance suite build was cut short locally by shared-tmpfs exhaustion; CI carries the conformance rows.
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 all three import maps (polyengine-impl, conformance driver, browser bundle) to the polyengine v0.4.0 release, and the runner core to polymorph-test v0.2.1: the
@jsr/polymorph__testnpm tree plus the fourcomponent-test-*cargo revs and the conformance.yml action refs (one release, 9f9e4d5).Upstream's one breaking change (the A19 err-result brand-key rename) is internal to the engine;
wasmtime-impl'sWitErroralias is the WIT-generated error type, unrelated, and the impl already recognizes values by@polyengine/protocolpredicates.Package version 0.4.0: the published deno.json's
@polyengine/runtimerange moves to^0.4.0— a resolution-level break for consumers holding 0.3.0 pins.Gates locally:
just polyengine-check(pin gates + 13/13 impl tests + driver deno checks),cargo check --workspace. The local conformance suite build was cut short by shared-tmpfs exhaustion (environment, not code); the conformance workflow carries those rows.