Repository navigation
fix: pass the release app key to the release tail - #244
Merged
Merged
Conversation
The release commit to main is refused unless the release tail can tag as the app; this explicit secrets list never handed GH_APP_PRIVATE_KEY over, so v1.18.47's VERSION and CHANGELOG commit never landed.
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.
The release commit to main only lands when the release tail can tag as the app, and this workflow's explicit secrets list never handed GH_APP_PRIVATE_KEY over. So v1.18.47 tagged and published fine, but its VERSION and CHANGELOG commit was refused by the ruleset.
Done when the next loader release's Tag & Release shows no GH_APP_PRIVATE_KEY warning and its release commit lands on main.