Skip to content

@deltic/protocol 0.2.0: A10 renamed its exports; the JSR package must move too - #119

Merged
lannbot merged 1 commit into
mainfrom
protocol-0.2.0
Aug 12, 2026
Merged

@deltic/protocol 0.2.0: A10 renamed its exports; the JSR package must move too#119
lannbot merged 1 commit into
mainfrom
protocol-0.2.0

Conversation

@lannbot

@lannbot lannbot commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

A10 (#114) renamed @deltic/protocol's exports without bumping the package version. JSR versions are immutable and the release workflow deliberately skips already-published versions, so every post-A10 prerelease depends on jsr:@deltic/protocol@^0.1.0 and resolves to the pre-A10 content — hard SyntaxError at module load for every consumer. All six polymorph migration tracks hit it simultaneously.

One-line fix: protocol → 0.2.0 (semver-honest — exports were removed). deno publish rewrites the workspace dep to ^0.2.0 on the next prerelease; consumers re-pin to that prerelease. Immutable 0.1.0 keeps serving pre-A10 prereleases (^0.1.0 never crosses 0.2.0). Contract A10 status entry gets the release note.

Gates: just test-protocol publish-check test-bundle green (publish-check simulates @deltic/protocol@0.2.0).

Follow-up guard tracked separately: CI should fail when protocol/src changes without a protocol/deno.json version bump.

… move too

A10 (#114) renamed WitError/isWitError/WIT_ERROR to ComponentException/
isComponentException/COMPONENT_EXCEPTION in @deltic/protocol's export
surface without bumping the package version. JSR versions are immutable
and the release workflow deliberately skips already-published versions,
so every post-A10 prerelease (runtime@0.1.0-pre.g{3c8c0e9..b297834})
resolves jsr:@deltic/protocol@^0.1.0 to the pre-A10 0.1.0 content and
fails at module load:

  SyntaxError: The requested module 'jsr:@deltic/protocol@^0.1.0' does
  not provide an export named 'isComponentException'

Found by all six polymorph consumer-migration tracks simultaneously.

Fix: bump protocol to 0.2.0 (semver-honest: exports were removed).
deno publish rewrites the workspace dep to ^0.2.0 at the next
prerelease, which consumers then pin. Immutable 0.1.0 keeps serving
pre-A10 prereleases correctly (^0.1.0 never resolves across 0.2.0).
Release note recorded in the contract's A10 status entry.
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