fix: match Release Please root title - #34
Merged
Merged
Conversation
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.
Summary
cometapiidentity for the temporary branch while excluding it from the title and public tagReal-run evidence
Manual preparation run 30435342700 created the correct
0.1.1PR #33, then the postcondition validator failed because it expectedchore(main): release cometapi 0.1.1. The pinned strategy log showedcomponent:empty,include-component-in-tag=false, and the actual titlechore(main): release 0.1.1. No tag, GitHub Release, live request, or npm publication occurred;RELEASE_PLEASE_ENABLEDwas restored tofalsebefore this fix.Verification
npm run verify:offline(13 files, 359 tests)npm run check:self-containedon committed HEADnpm run actionlintgit diff --check