fix(ci): set last-release-sha so release-please finds its anchor#152
Merged
Conversation
…r manual v2.0.0 tag
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
Release Please was not creating a Release PR because it couldn't find a SHA anchor for
v2.0.0. The release was created manually (not by release-please), so it has noautorelease: taggedlabel that release-please uses to locate the last release commit.Fix: add
last-release-shatorelease-please-config.jsonpointing to the merge commit of PR #147 (the commit tagged asv2.0.0). After release-please successfully creates and merges its first Release PR, it will manage the anchor itself going forward — this field can be removed.Test plan
2.1.0