ci: bump release-drafter to v7.3.0 and drop pull_request trigger#18
Merged
Conversation
Dependabot bumped release-drafter from v6 to v7.2.1 in #14, but the update failed CI. Root cause: v7 changed how target_commitish is resolved on pull_request events. v6 fell back to the default branch; v7 passes GITHUB_REF through unchanged, which on a PR event is refs/pull/N/merge. The GitHub Releases API rejects that — target must be a branch name or commit SHA. Two cleanups in one: 1. Remove pull_request from the on: block. release-drafter v7 moved autolabeling into a separate action (release-drafter/release-drafter/autolabeler). The drafter step itself only needs push events to develop/main to keep the draft current. 2. Pin to v7.3.0 (latest), not v7.2.1 (dependabot's stale snapshot). Closes the loop that #14 opened. Future dependabot bumps inside the v7 line will be clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-Authored-By: amcheste <13696614+amcheste@users.noreply.github.com>
amcheste
approved these changes
May 12, 2026
This was referenced May 12, 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.
Fixes the failure that closed dependabot #14.
Root cause
release-drafter v7 changed how
target_commitishis resolved onpull_requestevents. In v6, the action defaulted to the configured branch; in v7 it passesGITHUB_REFthrough unchanged. On a PR event,GITHUB_REFisrefs/pull/N/merge— which the GitHub Releases API rejects as atarget_commitishvalue (must be a branch name or commit SHA).Failure log from #14:
Two changes in one PR
Remove
pull_request:fromon:. release-drafter v7 split autolabeling into a separate action (release-drafter/release-drafter/autolabeler@v7). The drafter step only needspushevents on develop/main to keep the draft current —pull_requestwas load-bearing only for the (now-removed) bundled autolabel feature.Pin to v7.3.0, not v7.2.1. v7.3.0 is the latest at the time of writing; dependabot's chore: bump release-drafter/release-drafter from 6.4.0 to 7.2.1 #14 was bumping to an older snapshot.
Follow-up
The same workflow shape lives in
repo-template— a mirror PR will follow there so future-spawned repos don't inherit the bug.