Repository navigation
ci: set the first release's version to 0.1.0 - #1247
Merged
Merged
Conversation
The manifest said 0.1.0 had been released, but no v0.1.0 tag or release exists, so release-please proposed 0.2.0 with a compare link from a missing v0.1.0 tag. With 0.0.0 as the last released version, the feat commits since the bootstrap commit give 0.1.0 (bump-minor-pre-major), the version the package.json files already carry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J9aRFT65SaRk7Hr67vQV1U
With the manifest at 0.0.0, release-please treats the package as never released and uses its default first version, 1.0.0, so the release PR became 1.0.0. initial-version is used only for that first release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J9aRFT65SaRk7Hr67vQV1U
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
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.
After #1245 set the manifest to
0.0.0, release-please rewrote the release PR #1226 as 1.0.0. Release-please treats a manifest version of0.0.0as "never released" (manifest.ts) and then falls back to its default first version,1.0.0(base.tsinitialReleaseVersion).This adds
"initial-version": "0.1.0"to the package config. It is read only for that first release, so it needs no removal afterwards. After this merges, release-please should rewrite #1226 as 0.1.0.The owner asked on 2026-11-04 at 00:30 UTC for the first release to be 0.1.0.
Generated by Claude Code