polyengine 0.6.3; @polymorph/test 0.3.0; @polymorph/websocket 0.6.0 - #64
Merged
Conversation
Bump the conformance driver's exact pins to the polyengine v0.6.3
lockstep line and @polyengine/protocol 0.3.1. polyengine 0.6.0 removed
CliOptions.passthrough, so the driver's wasi({ cli }) drops it.
The runner core moves to @polymorph/test 0.3.0 (jsr pin + npm alias):
0.2.1's polyengine-worker-main called ct-runner internals 0.6.0
un-exported, which broke the browser leg; 0.3.0 drives runSuite.
The published host module takes @polyengine/protocol ^0.3.1 — a
protocol minor bump, breaking under the caret-honest scheme — so
@polymorph/websocket goes 0.5.0 -> 0.6.0.
Gates: polyengine-module-check, runner-js-pin-check, check-js,
exam-polyengine, run-polyengine (55/55), run-polyengine-browser
(55/55), run-wasmtime, run-composed, aggregate, matrix-check (no diff).
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
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 the conformance driver's exact pins to polyengine 0.6.3 and
@polyengine/protocol0.3.1. polyengine 0.6.0 (polymorph-components/polyengine#260) removedCliOptions.passthrough; the driver'swasi({ cli })drops it.The runner core moves to
@polymorph/test0.3.0 (jsr pin + npm alias). 0.2.1'spolyengine-worker-maincalled ct-runner internals that 0.6.0 un-exported (testContextImportRecord is not a functionin the browser leg); 0.3.0 (polymorph-components/polymorph-test#106) drivesrunSuite.The published host module
js/polyenginetakes@polyengine/protocol@^0.3.1— a protocol minor bump, breaking under the caret-honest scheme — so@polymorph/websocketgoes 0.5.0 → 0.6.0. Publish viajsr-publishafter merge (polymorph-iroh's host follows).Gates:
polyengine-module-check(17/17),runner-js-pin-check,check-js,exam-polyengine,run-polyengine(55/55),run-polyengine-browser(55/55),run-wasmtime,run-composed,aggregate,matrix-check(no diff).Automerge armed.