ci(release-please): unlock la PR de release avant le commentaire post-merge#258
Merged
Merged
Conversation
Locked release-please PRs make the action exit non-zero when it tries to post the post-merge tagged comment, even though the tag and the GitHub release are already created. Add a pre-step that detects the latest release PR via gh search, checks its locked state, and unlocks it so release-please can finish its cycle cleanly.
Contributor
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (5)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Quand la PR `chore(main): release …` est verrouillée (manuellement ou via une politique repo), release-please plante en exit non-zero au moment de poster son commentaire de feedback — même si le tag git et la release GitHub ont déjà été créés.
Ce patch ajoute un step avant `Run Release Please` qui :
Ainsi release-please peut finir son cycle proprement (label `autorelease: tagged`, commentaire de feedback). Aucune entrée utilisateur non-trustée n'est utilisée dans le shell.
Test plan