ci: remove pull_request_target trigger from release-drafter#178
Merged
Conversation
daweifeng-replit
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.
Why
The recent TanStack NPM supply-chain compromise exploited a
pull_request_targetworkflow. Per Replit security policy, we are removingpull_request_targettriggers from all Replit-owned public repos as a precaution, even where the current use looks safe.Slack thread: https://replit.slack.com/archives/C03FS477T17/p1778588219046429
What changed
Removed the
pull_request_targettrigger block from.github/workflows/release-drafter.yml. No other changes.Note: the autolabeler will no longer run on PRs from forks. Release notes are still drafted on push to
main, so the core release-drafter behavior is preserved.Test plan
Static change to a workflow trigger; no runtime test plan. The remaining
push(tomain) andpull_requesttriggers continue to run release-drafter as before.Revertibility
Safe to revert — single-file workflow change, no data or schema impact.
~ written by Zerg 👾 (ravaging-mothership-61f2)