ci: upgrade release-drafter to v7.1.1 with separate autolabeler#598
Merged
tykeal merged 1 commit intoFutureTense:mainfrom Apr 15, 2026
Merged
ci: upgrade release-drafter to v7.1.1 with separate autolabeler#598tykeal merged 1 commit intoFutureTense:mainfrom
tykeal merged 1 commit intoFutureTense:mainfrom
Conversation
Split the combined release-drafter workflow into two: - release-drafter.yaml: drafts releases on push to main - autolabeler.yaml: labels PRs using the v7 /autolabeler subcommand Also upgrades harden-runner from v2.15.0 to v2.16.1. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Andrew Grimberg <tykeal@bardicgrove.org>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR upgrades the repository’s Release Drafter automation to v7.1.1 and adopts the v7+ pattern of splitting release drafting and PR autolabeling into separate workflows, enabling tighter permissions and simpler triggers.
Changes:
- Upgrade
release-drafteraction to v7.1.1 (andharden-runnerto v2.16.1). - Simplify Release Drafter workflow to run only on
pushtomain. - Add a dedicated Autolabeler workflow using the v7
/autolabeleraction path with scoped permissions and fork-safe triggering.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/release-drafter.yaml | Upgrades Release Drafter to v7.1.1, scopes triggers to push only, and simplifies concurrency/permissions. |
| .github/workflows/autolabeler.yaml | Introduces a separate autolabeling workflow using the v7 autolabeler action path with minimal permissions and fork-aware execution. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Summary
Upgrade release-drafter from v6.2.0 to v7.1.1 and split the combined workflow into two dedicated workflows following the v7+ pattern:
Changes
.github/workflows/release-drafter.yaml— Simplified to only run onpushto main. Upgraded to v7.1.1 and harden-runner v2.16.1. Removed PR triggers and debug step..github/workflows/autolabeler.yaml(new) — Dedicated PR autolabeling using the v7/autolabelersubcommand. Runs onpull_requestandpull_request_targetwith minimal permissions.Why
Release-drafter v7+ separates the autolabeler into its own action path (
release-drafter/release-drafter/autolabeler), enabling:contents: write, autolabeler only needspull-requests: write)