fix(ci): anchor release-please to the 1.0.0 commit - #16
Merged
Conversation
The first `pnpm release:pr` produced a 98-entry changelog reaching back into pre-public history — "added support for storing dark mode", "add dagre and graphlib as window globals" — because release-please had nothing to measure from. `bootstrap-sha` was removed when 1.0.0 landed, on the reasoning that from then on the last git tag would be the anchor. No tag was ever created: 1.0.0 was a version in the manifest, not a release. So the walk started from the first commit in the repository. `last-release-sha` names the commit 1.0.0 corresponds to, which is what release-please wants when a version has no tag behind it. The next release covers the nine commits since, not all 118. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
| Commit | Scanned at | New | Resolved | Net |
|---|---|---|---|---|
3acbf0c < |
2026-08-17 01:39 UTC | 0 | 0 | 0 |
Last scanned: 3acbf0c · 2026-08-17 01:39 UTC
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.
Running
pnpm release:prfor real surfaced a defect that no dry run had: the release pull request it opened (#15) carried a 98-entry changelog reaching back into pre-public history — "added support for storing dark mode", "add dagre and graphlib as window globals", "basic layout styles".Cause
bootstrap-shawas removed when 1.0.0 landed, on the reasoning that from then on the last git tag would be the anchor. No tag was ever created. 1.0.0 was a version in the manifest, not a release —release-please github-releasereports "Would tag 0 releases" precisely because there is no merged release pull request behind it. With no tag and no bootstrap, the commit walk started at the first commit in the repository.Fix
last-release-shanames the commit that 1.0.0 corresponds to (5e0ec6d, the merge of #9), which is what release-please wants when a version has no tag behind it.It belongs at the root of the config, not inside
packages["."]— the same placebootstrap-shaoccupied. Nesting it silently does nothing, which cost a round here and is worth knowing.Verified, not assumed
Run against this branch's own config with
--target-branch, so the tool read the change rather than main's:And all six are genuinely post-1.0.0:
After merging
Re-run
pnpm release:pr— it updates #15 in place with the correct changelog. Do not merge #15 as it stands; it would write 98 entries of internal history intoCHANGELOG.mdand tag them 1.1.0.🤖 Generated with Claude Code