protocol: 0.2.1 — republish the A20 exports burned out of 0.2.0 - #221
Merged
Conversation
#216 merged first and its green-main prerelease published @polyengine/protocol@0.2.0 (brand-key rename only) at 17:42; #219's merge resolution kept 'protocol stays at 0.2.0: A19's rename and A20's exports ride the same pending release' — but the version was no longer pending, so every publish since skips protocol as already-published and the A20 surface (toCloneable/fromCloneable, REALM_LOCAL, the realm-local pill) never shipped. Meanwhile runtime/src/embedder/mod.ts imports that surface: runtime@0.4.0-pre.g7fb65ed fails at import time when installed from either registry (the bundled embedder asset is unaffected — it inlines workspace sources). Patch, not minor: the A20 additions are additive and the minor is reserved as the breaking signal (README §Consuming). The publish rewrite floors the lockstep cross-dep at ^0.2.1, which is the honest constraint. A publish-time content-identity guard to make this class of tear fail loudly is coming separately.
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.
Published
@polyengine/protocol@0.2.0is a husk: #216 merged first and its green-main prerelease burned the 0.2.0 version with the brand-key rename only; #219's merge resolution assumed the version was still pending and rode it, so the A20 exports (toCloneable/fromCloneable,REALM_LOCAL, the realm-local pill) never shipped — every publish since skips protocol as already-published.runtime/src/embedder/mod.tsimports that surface from@polyengine/protocol, soruntime@0.4.0-pre.g7fb65edfails at import time from either registry.Patch bump (additive surface; the minor stays the breaking signal). Once this merges and the green-main prerelease publishes protocol@0.2.1, the v0.4.0 cut is unblocked.
A publish-time content-identity guard (in-tree protocol vs the published version's JSR file hashes) follows in a separate PR so this tear class fails loudly instead of shipping.