ci: bump release-drafter to v7.3.0 and drop pull_request trigger#83
Merged
Conversation
Family-wide fix following amcheste/engineering-handbook#18. release-drafter v7 changed how target_commitish is resolved on pull_request events: v6 fell back to the configured default branch, v7 passes GITHUB_REF through unchanged (refs/pull/N/merge on a PR event). The Releases API rejects that value, so the action fails on every PR. v7 also moved autolabeling into a separate action, so the drafter step only needs push events on develop/main. 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 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
2 participants
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.
Family-wide fix following engineering-handbook#18 and repo-template#13.
Why
release-drafter v7 changed how
target_commitishis resolved onpull_requestevents:GITHUB_REFthrough unchanged. On a PR event, that'srefs/pull/N/merge— which the GitHub Releases API rejects (target must be a branch or commit SHA).Result: the action fails on every PR with
Validation Failed: target_commitish(or runs silently broken on v7 if no v6 dependabot bump surfaced it yet).Two changes
pull_request:fromon:. v7 split autolabeling into a separate action (release-drafter/release-drafter/autolabeler@v7). The drafter step only needspushevents on develop/main.