ci: Wire up Release Drafter autolabeler#2146
Merged
Merged
Conversation
The autolabeler rules in release-drafter.yml were never executed: the main release-drafter action only drafts releases, it does not apply labels. Labeling is a separate sub-action (release-drafter/release-drafter/autolabeler). As a result PRs were not auto-labeled and the changelog grouping relied on manual labels. Add a dedicated `autolabel` job (PRs only) using the autolabeler sub-action, and gate the existing draft job to push events so each only runs where it applies.
github-actions
Bot
added
the
code-quality
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.
Problem
The
autolabelerrules added in #2143 were never actually executed. The mainrelease-drafter/release-drafteraction only drafts releases — it parses the full config (hence the deprecation warnings in its logs) but does not apply labels. Labeling is a separate sub-action:release-drafter/release-drafter/autolabeler.Consequences observed:
code-quality) and ci: strip Conventional-Commit prefix from changelog entries #2144 (ci) were labeled manually, not by the action.Since the changelog draft groups by label, an unlabeled merged PR falls into the uncategorized bucket — the exact drop we set out to fix.
Fix
autolabeljob (PRs only) using therelease-drafter/release-drafter/autolabelersub-action, withpull-requests: write.update_release_draftjob topushevents, so each job only runs where it applies (no wasted draft run per PR).Follow-up to #2143 / #2144.
Verification
After merge I'll confirm a new PR gets labeled by
github-actions(not manually). Also worth a separate cleanup: relabel #2144ci->code-quality, and deprecate the stalecilabel (not part of the new scheme).