releases: adopt the caret-honest 0.1.0 regime; deltic pin to 0.1.0 - #95
Merged
Conversation
The polymorph family adopts deltic's release scheme: everything stays 0.x/unstable, but releases are caret-honest — within a minor line they stay backward-compatible, and anything breaking bumps the minor. Consumers pin a release's commit and bump deliberately. README and the npm facade's stability wording now say so; the facade's version drops 0.2.0 -> 0.1.0 (never registry-published, so the number was a free label) to start the lockstep at the v0.1.0 tag this commit is cut as. deltic: bump the JSR pin 0.1.0-pre.g078aa15 -> 0.1.0, the first non-pre deltic release. Upstream renamed @deltic/wasi-shims -> @deltic/wasi and wasiShims()/WasiShims/WasiShimsOptions -> wasi()/WasiImports/WasiOptions; call sites and the bundle re-exports follow. @deltic/protocol resolves at 0.2.0 (stable, gate-excluded by name). Goldens unchanged: check, verify-deltic, verify-viewer green.
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.
First step of the polymorph-wide v0.1.0 release rollout (deltic's scheme, org-wide): everything stays 0.x/unstable, but releases are caret-honest — within a minor line they stay backward-compatible, and anything breaking bumps the minor. Consumers pin a release's commit and bump deliberately. This repo goes first in topological order; the sibling repos follow, bumping their polymorph-test pins to the released commit.
@deltic/wasi-shims→@deltic/wasi(wasiShims()/WasiShims/WasiShimsOptions→wasi()/WasiImports/WasiOptions); call sites and the bundle re-exports follow.@deltic/protocolresolves at 0.2.0 (stable line, gate-excluded by name). Pins stay exact — the pin gate compares specifier text against lock resolutions and module URLs, and exact pins keep one bump = one reviewable diff; caret-honest is the release policy, not a range specifier.Gates:
just check,just verify-deltic,just verify-viewer— all green, goldens unchanged.After merge: I tag the merge commit
v0.1.0and publish the GitHub release; downstream repos then pin it.