Sync release-please manifest to 2.3.1#48
Merged
Merged
Conversation
Versions 2.2.x and 2.3.0/2.3.1 were published manually with the release-please PAT in a broken state (Bad credentials in the release-please workflow), so the manifest never moved off 2.0.0. Catch it up to the current published version so release-please picks up correctly after the PAT is refreshed and resumes cutting release PRs.
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-manifest.jsonfrom2.0.0→2.3.1to match the currentpackage.jsonversion.Why
The release-please workflow has been failing with
Bad credentialsfor a while (theRELEASE_PLEASE_ATPAT is expired/revoked), so versions 2.2.x and 2.3.0/2.3.1 were published manually. Because release-please never ran, the manifest never updated and still says 2.0.0.Once the PAT is refreshed and release-please resumes, it would otherwise scan conventional commits from 2.0.0 onward and propose releasing everything between 2.0.0 and 2.3.1 again. Catching the manifest up to 2.3.1 here lets release-please pick up from where we actually are.
Test plan
.release-please-manifest.jsonv2.3.1tag to point at the merge commit so the tag lives in main's history