fix: revert autolabeler to release-drafter v6.4.0#115
Merged
Conversation
## What Reverted the auto-labeler workflow from the release-drafter v7 autolabeler sub-action back to the v6.4.0 main action with disable-releaser: true. ## Why The v7 autolabeler sub-action hardcodes a strict check for the pull_request event and rejects pull_request_target. Since this reusable workflow is called from a pull_request_target trigger (required for labeling fork PRs with write permissions), the autolabeler fails on every fork PR. ## Notes - The v6 action uses GITHUB_TOKEN via env rather than the token input - release-drafter v7 is still used in the release workflow; only the autolabeler is pinned to v6 - Consider opening an upstream issue on release-drafter to support pull_request_target in the v7 autolabeler Signed-off-by: jmeridth <jmeridth@gmail.com>
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.
What
Reverted the auto-labeler workflow from the release-drafter v7 autolabeler sub-action back to the v6.4.0 main action with
disable-releaser: true.Why
The v7 autolabeler sub-action hardcodes a strict check for the
pull_requestevent and rejectspull_request_target. Since this reusable workflow is called from apull_request_targettrigger (required for labeling fork PRs with write permissions), the autolabeler fails on every fork PR.Notes
GITHUB_TOKENvia env rather than thetokeninput — this is how v6 expected auth to be configuredpull_request_targetin the v7 autolabeler