polyengine 0.4.0; @polymorph/websocket 0.4.0 - #59
Merged
Conversation
Bump both import maps to the polyengine v0.4.0 release and the runner core to @polymorph/test 0.2.1 (JSR pin, @jsr/polymorph__test npm tree, cargo revs and CI action refs all naming the one polymorph-test v0.2.1 release, 9f9e4d5). A19 fallout: upstream renamed the err-result brand key polyengine.witError/1 -> polyengine.componentException/1; the hand-rolled foreign-copy brand test updates its literal key exactly as its own comment demands (a brand bump upstream must fail here and force the recognition sites to be revisited). Package version 0.4.0: the published deno.json's @polyengine/runtime range moves to ^0.4.0, which is a resolution-level break for consumers holding 0.3.0 pins. Gates: exam-polyengine, runner-js-pin-check, polyengine-module-check (14/14), just check (rust legs), all four conformance rows (220 results, 0 failing), matrix-check clean. check-js and wpt::parity fail identically on unmodified origin/main (Node 24 ESM/CJS resolution, pre-existing).
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 both import maps to the polyengine v0.4.0 release, and the runner core to polymorph-test v0.2.1 everywhere it is named (JSR pin,
@jsr/polymorph__testnpm tree, cargo revs, CI action refs — one release, 9f9e4d5).A19 fallout: upstream renamed the err-result brand key
polyengine.witError/1->polyengine.componentException/1; the hand-rolled foreign-copy brand test updates its literal key exactly as its own comment demands (a brand bump upstream must fail there and force the recognition sites to be revisited).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:
exam-polyengine,runner-js-pin-check,polyengine-module-check(14/14),just checkRust legs, all four conformance rows (220 results, 0 failing),matrix-checkclean.check-jsandwpt::parityfail identically on unmodified origin/main (pre-existing Node 24 ESM/CJS resolution issue, unrelated).