fix(ci): restore pull_request_target for mirror-changelog - #109
Merged
Conversation
…ate PRs need a write token)
wangauone
force-pushed
the
fix/mirror-changelog-trigger
branch
from
August 17, 2026 23:35
34bdf14 to
fbcb357
Compare
dishaprakash
approved these changes
Aug 18, 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
3 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.
Renovate PRs come from a fork (forking-renovate), and
pull_requestgives fork PRs a read-only token, so the changelog workflow's PR-body update 403s (e.g. #106).Restore
pull_request_targetso it gets a write token. Safe here (no PR-code checkout, gated on renovate-bot, API-only body update), so the zizmor finding is suppressed inline.