polyengine 0.5.0 - #104
Merged
Merged
Conversation
Bump js/runner-polyengine's five lockstep pins to the polyengine v0.5.0 release and adopt the A22 protocol/runtime split: the runtime's embedder no longer re-exports the host-ABI vocabulary (error classes, brands, handle types), so browser-bundle-entry.ts re-exports @polyengine/protocol (exact-pinned 0.2.2) alongside the embedder — downstream bundled workers keep seeing ComponentException and friends off the bundle. Doc comments that hung module identity on "instanceof ComponentException" now state the real post-A22 constraint (stateful handle interop needs one runtime copy; protocol vocabulary is cross-copy safe). polyengine-pin-gate excludes @polyengine/protocol from the lockstep extraction (it versions independently and may now be pinned directly). The published @polymorph/test surface is untouched: the injected-engine contract reads only machinery off the bundle, so no version bump and no downstream @jsr/polymorph__test churn. Gates: build, polyengine-pin-gate, verify-polyengine (bundle + node selftests + golden diff), deno check --frozen.
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 js/runner-polyengine's five lockstep pins to the polyengine v0.5.0
release and adopt the A22 protocol/runtime split: the runtime's
embedder no longer re-exports the host-ABI vocabulary (error classes,
brands, handle types), so browser-bundle-entry.ts re-exports
@polyengine/protocol (exact-pinned 0.2.2) alongside the embedder —
downstream bundled workers keep seeing ComponentException and friends
off the bundle. Doc comments that hung module identity on "instanceof
ComponentException" now state the real post-A22 constraint (stateful
handle interop needs one runtime copy; protocol vocabulary is
cross-copy safe).
polyengine-pin-gate excludes @polyengine/protocol from the lockstep
extraction (it versions independently and may now be pinned directly).
The published @polymorph/test surface is untouched: the injected-engine
contract reads only machinery off the bundle, so no version bump and no
downstream @jsr/polymorph__test churn.
Gates: build, polyengine-pin-gate, verify-polyengine (bundle + node
selftests + golden diff), deno check --frozen.