Skip to content

polyengine 0.4.0; @polymorph/test 0.2.1 - #103

Merged
lannbot merged 1 commit into
mainfrom
polyengine-0.4.0
Aug 22, 2026
Merged

polyengine 0.4.0; @polymorph/test 0.2.1#103
lannbot merged 1 commit into
mainfrom
polyengine-0.4.0

Conversation

@lannbot

@lannbot lannbot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Bump the js/runner-polyengine pins to the polyengine v0.4.0 release (lockstep four at 0.4.0; @polyengine/protocol rides its own ~0.2.1 range in the regenerated lock).

The one upstream breaking change — err-result brand key polyengine.witError/1 -> polyengine.componentException/1 (A19) — is internal to the engine: this repo's runner code takes the embedder bundle as an argument and never references the brand key, and verify-polyengine's goldens are unmoved.

Patch release 0.2.1: the package's own exports and behavior are unchanged; only the repo-side engine pin moves. (Bump-together contract: consumers set their cargo rev and @jsr/polymorph__test version to this release once cut.)

Gates: just polyengine-pin-gate, just check, just verify-polyengine, just all — all green locally.

Bump the runner-polyengine pins to the polyengine v0.4.0 release
(lockstep four at 0.4.0; @polyengine/protocol rides its own ~0.2.1
range in the regenerated lock). The one upstream breaking change —
err-result brand key polyengine.witError/1 -> componentException/1
(A19) — is internal to the engine: this repo's runner code takes the
embedder bundle as an argument and never touches the brand key, and
verify-polyengine's goldens are unmoved. Patch release 0.2.1: the
package's own exports and behavior are unchanged.

Gates: just polyengine-pin-gate, check, verify-polyengine, all — green.
@lannbot
lannbot merged commit 9f9e4d5 into main Aug 22, 2026
3 checks passed
@lannbot
lannbot deleted the polyengine-0.4.0 branch August 22, 2026 22:32
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