chore: add maintained-branch release check workflow#24523
Open
mshabarov wants to merge 5 commits into
Open
Conversation
Adds scripts/checkReleases.js and a scheduled GitHub Actions workflow
that report which maintained branches have unreleased feat:/fix: changes
worth a patch release. Maintained branches are read from
on.push.branches in validation.yml, so there is no second list to keep
in sync. chore:/refactor: and other prefixes are ignored.
The workflow keeps one issue per branch so each release can be tracked
and assigned individually. It upserts by a stable title (editing the
existing open issue instead of creating duplicates) and auto-closes a
branch's issue once it is fully released.
Issue title (branch-only so it stays stable across release cycles):
Release pending: <branch>
Issue body template:
Branch `<branch>` has **<n>** unreleased `feat:`/`fix:` commits since `<lastTag>`.
Suggested next release: `<nextVersion>`
### Changes to release
- <commit subject> (<short-sha>)
...
---
_Auto-generated by `scripts/checkReleases.js` from
`.github/workflows/validation.yml`. Last updated <date>. Assign this
issue to whoever owns the `<branch>` release._
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
tltv
reviewed
Jun 17, 2026
tltv
left a comment
Member
There was a problem hiding this comment.
Could this go in first without scheduled trigger so that it can be test-run manually before enabling cron trigger on every Monday?
Contributor
|
some experience from the scheduled trigger.. it will not run on the schedule time, if there is no enough resource.. |
Contributor
Author
no objections, removed for now. |
|
tltv
approved these changes
Jun 18, 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.



Adds scripts/checkReleases.js and a scheduled GitHub Actions workflow that report which maintained branches have unreleased feat:/fix: changes worth a patch release. Maintained branches are read from on.push.branches in validation.yml, so there is no second list to keep in sync. chore:/refactor: and other prefixes are ignored.
The workflow keeps one issue per branch so each release can be tracked and assigned individually. It upserts by a stable title (editing the existing open issue instead of creating duplicates) and auto-closes a branch's issue once it is fully released.
Issue title (branch-only so it stays stable across release cycles):
Issue body template: