Repository navigation
ci(release): close reminders for superseded releases (#1327) - #1474
Merged
Merged
Conversation
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-code · BYOK · MIT |
This was referenced Oct 15, 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
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.
What
Part 3 of 4 of the release-signature reminder (parts 1 and 2 are #1472 and #1473, merged).
scripts/release-signature-reminder.shalso closes openSign release vX.Y.Z (minisign)issues for releases that are no longer the latest.uteke upgradeinstalls only the latest release, so an old reminder would nag about something nobody can install. Only trusted-author issues with the exact title are touched, at most 20 per run, each closed with an explanatory comment.--dry-runonly prints.The test script gets the matching cases (stale reminder closed, current one kept, untrusted author ignored, dry run).
Why
A backport patch can be published after a newer minor, or a release can be skipped without being signed. Without this the old issue stays open forever.
Testing
bash scripts/tests/release-signature-reminder.test.sh: all checks pass.bash -nis clean. No workflow is added yet (part 4), so nothing runs from this PR.