Repository navigation
Keep one release-watch issue per stale pin - #19
Merged
Merged
Conversation
…ease The watch deduplicated by searching open issues for the latest release's version, so every week upstream shipped, the stale pin looked untracked and got a fresh issue: #13-#17 were all "Bump Slang 2026.16 -> ...". CLAUDE.md claimed it stayed quiet once any issue was open, which the code never did. It now looks for any open issue it filed itself (author is a bot, title starts "Bump Slang "), whichever release that issue named. If the title already names the latest release the run stays quiet; otherwise track-issue (formerly file-issue) retitles that issue and refreshes its body -- an edit, so nobody is notified again -- and only files a new one when none is open. The bump-branch check and the mode=bump path are unchanged. Dry-run locally: the check step with the pin forced to 2026.16 resolves latest 2026.19, finds no open issue and would file one; the matching run against the closed history picks #17 and classifies "-> 2026.18.3" as already tracked and "-> 2026.19" as needing a retitle; the issue step renders the body and picks create or edit. The edit itself is not exercised until upstream ships past the pin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Qodana for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2026.1.3
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
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 watch filed a new issue for every Slang release while the pin was stale (#13–#17, all for 2026.16), because it only looked for an open issue naming the latest release.
Now a stale pin keeps one tracking issue:
Bump Slang …) counts as tracking, whichever release it namedmode: bumpare unchangedCLAUDE.md's "Release watch" bullet now matches.
Dry-run locally (check step with the pin forced stale; matching logic against the closed issue history; issue step rendered without calling GitHub). The retitle path runs for real once upstream ships past 2026.19.
🤖 Generated with Claude Code