Skip to content

polyengine 0.5.0; @polymorph/webcrypto 0.5.0 - #397

Merged
lann merged 1 commit into
mainfrom
polyengine-0.5.0
Aug 23, 2026
Merged

polyengine 0.5.0; @polymorph/webcrypto 0.5.0#397
lann merged 1 commit into
mainfrom
polyengine-0.5.0

Conversation

@lannbot

@lannbot lannbot commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Adopt the A22 protocol/runtime split (upstream contracts/embedder-api.md
"The host-ABI surface and its version"): the published host module now
depends on @polyengine/protocol alone — its deno.json maps
jsr:@polyengine/protocol@^0.2.2 and nothing else, and every Stream /
ComponentException import in js/polyengine (src + tests) moves to
@polyengine/protocol. Engine releases that leave the host ABI untouched
no longer require touching this package.

The conformance driver stays an application: its five lockstep pins
bump to 0.5.0 and it gains an exact @polyengine/protocol@0.2.2 pin
(run.ts's graph reaches protocol through js/polyengine).

polyengine-pin-check learns the two-line world: one resolved
@polyengine/runtime version where the embedder is loaded, one resolved
@polyengine/protocol version repo-wide, and js/polyengine must resolve
no @polyengine/runtime at all.

Runner-core pins (@polymorph/test 0.2.1, cargo revs, action refs) are
untouched: polymorph-test's published surface is engine-agnostic and
did not change this cycle.

Gates: polyengine-module-check (38 tests), polyengine-pin-check, driver
deno task check, and the polyengine conformance leg (exit 0;
declared-debt failures only).

Adopt the A22 protocol/runtime split (upstream contracts/embedder-api.md
"The host-ABI surface and its version"): the published host module now
depends on @polyengine/protocol alone — its deno.json maps
jsr:@polyengine/protocol@^0.2.2 and nothing else, and every Stream /
ComponentException import in js/polyengine (src + tests) moves to
@polyengine/protocol. Engine releases that leave the host ABI untouched
no longer require touching this package.

The conformance driver stays an application: its five lockstep pins
bump to 0.5.0 and it gains an exact @polyengine/protocol@0.2.2 pin
(run.ts's graph reaches protocol through js/polyengine).

polyengine-pin-check learns the two-line world: one resolved
@polyengine/runtime version where the embedder is loaded, one resolved
@polyengine/protocol version repo-wide, and js/polyengine must resolve
no @polyengine/runtime at all.

Runner-core pins (@polymorph/test 0.2.1, cargo revs, action refs) are
untouched: polymorph-test's published surface is engine-agnostic and
did not change this cycle.

Gates: polyengine-module-check (38 tests), polyengine-pin-check, driver
deno task check, and the polyengine conformance leg (exit 0;
declared-debt failures only).
@lann
lann enabled auto-merge August 23, 2026 03:43
@lann
lann merged commit d4931d6 into main Aug 23, 2026
10 checks passed
@lann
lann deleted the polyengine-0.5.0 branch August 23, 2026 03:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants