chore(release): bump to 0.1.1 for the first npm publish - #183
Merged
Conversation
0.1.0 is not available as a release tag: a stale `v0.1.0` tag from 2026-08-09 already points at 90f66c6, far behind current main, and it predates release.yml so it never published anything. Rewriting a pushed tag on a public repo to reclaim the version is worse than spending a patch number, so 0.1.0 stays with that August snapshot and the first published version is 0.1.1. package-lock.json root and packages[""] are bumped in step so `npm ci` in the release workflow does not fail on a version mismatch. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
github-actions
Bot
added
area: tooling
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.
Summary
Version bump ahead of the first real npm publish.
paragentis still unclaimed on the registry; this is the version that will take the name.Why 0.1.1 and not 0.1.0. A stale
v0.1.0tag already exists onmain, created 2026-08-09 and pointing at90f66c6— far behind currentHEAD. It predates.github/workflows/release.yml(#174), so it never triggered a publish. Reclaiming0.1.0would mean force-retagging a tag that is already public. Spending a patch number is cheaper than rewriting public history, so0.1.0stays with that August snapshot and the first published version is0.1.1.package-lock.jsonroot andpackages[""]are bumped in the same commit sonpm ciin the release workflow does not fail on a version mismatch.node_modules/yocto-queue@0.1.0is deliberately untouched.Test plan
package.jsondiff is the version line only — no reformatting (an earlier rewrite unescaped—indescription; reverted)package-lock.jsondiff is root +packages[""]onlyrequire('./package.json').version→0.1.1, lock root andpackages[""]→0.1.1npm ciconfirms lock/manifest agreev0.1.1matchespackage.jsonso the ci(release): fail when the tag and package.json version disagree #180 version guard passes