release: 1.1.0#759
Merged
arjunkmrm merged 1 commit intoMay 6, 2026
Merged
Conversation
29a748c to
d187af7
Compare
3 tasks
arjunkmrm
added a commit
that referenced
this pull request
May 6, 2026
## Why PR #759 keeps proposing version `1.0.0` (downgrade from current `1.0.1`) and pulls a massive historical changelog into the diff. Root cause: commit [683a982](683a982) ("chore: pin first release to 1.0.0") carries a `Release-As: 1.0.0` footer that was meant to anchor the rebrand release. That footer should have been consumed once 1.0.0 shipped, but release-please keeps re-discovering it on every scan and overriding the computed version. ## What Adds `last-release-sha` to the package config, pinned to the v1.0.1 release commit (`5195545`). This tells release-please anything before this SHA is already released — don't scan it. Permanently moves the stale Release-As footer out of scan range. ## Expected effect After this lands, release-please will regenerate PR #759 (or open a new one) computing the next version correctly from commits after v1.0.1 — should be `1.1.0` (we have unreleased feat commits) or `1.0.2`. ## Test plan - [ ] Merge this PR - [ ] Verify release-please workflow runs and updates #759 - [ ] Confirm new version proposed is >= 1.0.2 and changelog only includes #761, #762
d187af7 to
d565d71
Compare
arjunkmrm
added a commit
that referenced
this pull request
May 6, 2026
## Why PR #763 attempted to use `last-release-sha` to skip the stale `Release-As: 1.0.0` footer in commit 683a982, but release-please's tag-based detection takes priority over `last-release-sha` when tags exist, so the field had no effect. PR #759 still proposes a 1.0.0 downgrade. ## What - Reverts the no-op config change from #763. - Adds `Release-As: 1.1.0` footer below — release-please uses the **last** `Release-As:` footer in scan range, so this overrides 683a982. 1.1.0 reflects the natural conventional-commit bump (feat in #762, fix in #761) from current 1.0.1. ## Note for merge Important: squash-merge must preserve the `Release-As: 1.1.0` footer in the squash commit body. The default `gh pr merge --squash` behavior keeps the PR body, so this footer will land. If using the GitHub UI, ensure the footer stays in the squash commit message. Release-As: 1.1.0
d565d71 to
cc5361d
Compare
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.
Automated Release PR
1.1.0 (2026-05-06)
⚠ BREAKING CHANGES
Features
Bug Fixes
Performance Improvements
Reverts
Documentation
Chores
Refactors
This PR was generated with Release Please. See documentation.