polyengine 0.5.0; @polymorph/iroh 0.5.0 - #90
Merged
Merged
Conversation
Adopt the A22 protocol/runtime split and bump to the polyengine v0.5.0
release plus the freshly published protocol-only siblings
(@polymorph/{webcrypto,websocket,webrtc-datachannels}@0.5.0).
host-polyengine stays an instantiating application by design, so it
keeps @polyengine/runtime machinery (instantiate, ComponentArtifacts)
on a ^0.5.0 caret; its vocabulary imports (ComponentException in
harness/run-endpoint/sockets) move to @polyengine/protocol@^0.2.2. The
experiments' shared config bumps its exact pins to 0.5.0 / protocol
0.2.2 and moves errors.ts/sockets.ts vocabulary the same way.
Module-identity comments are rewritten to the post-A22 truth: wasi is
protocol-only internally and the @PolyMorph siblings no longer couple
to @polyengine/runtime at all — only this repo's own embedder loads
constrain runtime identity now. exam-polyengine gains the complementary
assertion that @polyengine/protocol also resolves to exactly one
version (the identity-gate script already scoped its check to runtime
URLs).
Gates: build-components, deno task check (host-polyengine + all three
experiments), exam-polyengine (7/7 scenarios, one runtime 0.5.0, no raw
URLs), just check (fmt/clippy/validate-wit/test), matrix (13/13), bench
(budgets hold).
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.
Adopt the A22 protocol/runtime split and bump to the polyengine v0.5.0
release plus the freshly published protocol-only siblings
(@polymorph/{webcrypto,websocket,webrtc-datachannels}@0.5.0).
host-polyengine stays an instantiating application by design, so it
keeps @polyengine/runtime machinery (instantiate, ComponentArtifacts)
on a ^0.5.0 caret; its vocabulary imports (ComponentException in
harness/run-endpoint/sockets) move to @polyengine/protocol@^0.2.2. The
experiments' shared config bumps its exact pins to 0.5.0 / protocol
0.2.2 and moves errors.ts/sockets.ts vocabulary the same way.
Module-identity comments are rewritten to the post-A22 truth: wasi is
protocol-only internally and the @PolyMorph siblings no longer couple
to @polyengine/runtime at all — only this repo's own embedder loads
constrain runtime identity now. exam-polyengine gains the complementary
assertion that @polyengine/protocol also resolves to exactly one
version (the identity-gate script already scoped its check to runtime
URLs).
Gates: build-components, deno task check (host-polyengine + all three
experiments), exam-polyengine (7/7 scenarios, one runtime 0.5.0, no raw
URLs), just check (fmt/clippy/validate-wit/test), matrix (13/13), bench
(budgets hold).