chore(ci): take the release PR number from release-please's output - #62
Merged
Merged
Conversation
Listing by label raced GitHub's indexing: the previous run created the release PR at 00:14:03 and a label query 3 seconds later returned nothing, so 3.1.1 sat open. The action's own output is immediate; the label query stays as a retried fallback. Claude-Session: https://claude.ai/code/session_01F1stiNzuNtJXoXtiW9ZCbs
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
This was referenced Aug 4, 2026
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
2 participants
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.
Follow-up to #60, which moved the release-PR merge into the push-triggered job but still located the PR with
gh pr list --label 'autorelease: pending'. That raced GitHub's indexing and lost: release-please created PR #61 at00:14:03Z, the merge step queried at00:14:05.9Z, and the step logged "No pending release PR to merge." The release then sat open, which is the exact stall #60 was meant to remove.Now the PR number comes from
steps.release.outputs.pr, which the action sets in the same job and which needs no indexing and no label. The label query survives as a retried fallback (3 attempts, 5s apart) for the case where the action updates an existing PR without re-emitting the output.Note the commit prefix here is
chore(ci):on purpose. #60 usedfix(ci):, which release-please counted as a patch and turned into a pointless 3.1.1 release of a CI-only change. CI-only commits should usechoreso they do not cut a release.This one cannot be proven by reading, only by watching the next cycle: after this merges, the publish run should merge the open release PR by itself and 3.1.1 should land on PyPI with nobody clicking. I will confirm that it did.
https://claude.ai/code/session_01F1stiNzuNtJXoXtiW9ZCbs