chore(release): 0.1.1 - #10
Merged
Merged
Conversation
The v0.1.0 git tag points at the initial commit, which predates the publish workflow, and nothing was ever published under it. Rather than rewrite a pushed tag, cut the first npm release as 0.1.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Why
First npm release.
verifyis green (19/19), including the pack-and-consume gate added in #9, so the tarball is known to resolve through its ownexportsmap from a real consumer install.Why 0.1.1 and not 0.1.0
The
v0.1.0git tag already exists on the remote and points at6808789, the initial commit — which predates the publish workflow entirely. Nothing was ever published under it (registry.npmjs.org/ai-forms→ 404).Rewriting a pushed tag to point somewhere else is the kind of history edit that quietly breaks anyone who already fetched it, so the first npm release is cut as 0.1.1 instead. The cost is a version number that starts at
.1; the benefit is that no published ref ever changes meaning.What happens on merge
Tagging
v0.1.1onmaintriggers.github/workflows/publish.yml, which re-runsverify, refuses to publish if the tag andpackage.jsondisagree, and publishes with npm provenance (id-token: write) so the registry can attest the tarball was built by this workflow from this commit.🤖 Generated with Claude Code