Skip to content

ci: categorized release notes via auto-labeling - #10

Merged
vdemonchy merged 1 commit into
mainfrom
ci/categorized-release-notes
Jun 7, 2026
Merged

vdemonchy merged 1 commit into
mainfrom
ci/categorized-release-notes

Conversation

@vdemonchy

Copy link
Copy Markdown
Owner

What

Make GitHub's auto-generated release notes (already used by release.yml via gh release create --generate-notes) produce a categorized changelog instead of a flat "What's Changed" list.

  • .github/release.yml — groups merged PRs into 🛠 Breaking / 🎉 Features / 🐛 Bug Fixes / ⚡ Performance / 📚 Documentation / 🧹 Maintenance & CI / 📦 Other. Excludes bot PRs and anything labeled skip-changelog.
  • .github/workflows/label-pr.yml — GitHub categorizes strictly by PR label, but this project encodes change type in Conventional Commit titles. This workflow bridges the gap: it reads the title prefix and applies the matching label (feat→enhancement, fix→bug, perf→performance, docs→documentation, refactor/chore/ci/build/style/test→maintenance, !/BREAKING CHANGE→breaking-change).

Also created the three new labels the config references: performance, maintenance, breaking-change.

Notes

  • The labeler reads the title via the github-script JS context (not ${{ }} in a shell run:), so there's no command-injection vector. pull_request_target is used so fork PRs can be labeled; the PR's code is never checked out.
  • Existing PRs COSMIC applet + shared battery UX, udev fix, XInput charging #1–feat(gnome): open preferences from the panel menu #9 stay unlabeled (the labeler only fires going forward), so they'll land under 📦 Other until labeled by hand. This self-corrects for new PRs.
  • This PR is the first live test of the labeler — it should auto-tag itself maintenance.

🤖 Generated with Claude Code

Add .github/release.yml so `gh release create --generate-notes` groups
merged PRs into categories (Breaking/Features/Bug Fixes/Performance/
Documentation/Maintenance & CI/Other). GitHub categorizes strictly by
PR label, so add a label-pr workflow that maps Conventional Commit
title prefixes (feat/fix/perf/docs/refactor/chore/ci/...) to the labels
those categories key off, including breaking-change for `!`/BREAKING
CHANGE markers.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vdemonchy
vdemonchy merged commit 7507afb into main Jun 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant