Skip to content

chore: add maintained-branch release check workflow#24523

Open
mshabarov wants to merge 5 commits into
mainfrom
check-releases
Open

chore: add maintained-branch release check workflow#24523
mshabarov wants to merge 5 commits into
mainfrom
check-releases

Conversation

@mshabarov

Copy link
Copy Markdown
Contributor

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._

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>
@mshabarov mshabarov requested a review from tltv June 4, 2026 10:25
@github-actions github-actions Bot added the +0.0.1 label Jun 4, 2026
@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

Test Results

 1 452 files  ±0   1 452 suites  ±0   1h 25m 42s ⏱️ - 1m 31s
10 260 tests ±0  10 192 ✅ ±0  68 💤 ±0  0 ❌ ±0 
10 732 runs  ±0  10 663 ✅ ±0  69 💤 ±0  0 ❌ ±0 

Results for commit f9e6e09. ± Comparison against base commit 7f99632.

♻️ This comment has been updated with latest results.

@mshabarov mshabarov requested a review from ZheSun88 June 8, 2026 08:02

@tltv tltv left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this go in first without scheduled trigger so that it can be test-run manually before enabling cron trigger on every Monday?

@ZheSun88

Copy link
Copy Markdown
Contributor

some experience from the scheduled trigger.. it will not run on the schedule time, if there is no enough resource..
we have builds in platform, scheduled at 9 am, normally the actual running time is around one hour later.

@mshabarov

Copy link
Copy Markdown
Contributor Author

Could this go in first without scheduled trigger so that it can be test-run manually before enabling cron trigger on every Monday?

no objections, removed for now.

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: 🔎Iteration reviews

Development

Successfully merging this pull request may close these issues.

3 participants