Repository navigation
fix: version_release workflow fails for fork PRs - #295
Merged
Merged
Conversation
pull_request workflows triggered by fork PRs receive no secrets, so checkout failed with "Input required and not supplied: token" (MS3_BOT_TOKEN empty). pull_request_target runs in the base repo context with secrets. Safe because the job only checks out the base branch.
johentsch
force-pushed
the
fix/release-workflow-fork-prs
branch
from
October 7, 2026 21:01
e603a89 to
de2e1ca
Compare
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.
Problem
version_release.ymlfailed on merged PRs from forks (e.g. run 37618258202, head repoe7mac/corelli) withInput required and not supplied: token. Workflows triggered bypull_requestfrom forks get no secrets, sosecrets.MS3_BOT_TOKENwas empty (Secret source: Nonein the log).Fix
Trigger on
pull_request_target(types:closed) instead. It runs in the base repo context with secrets available. This is safe because the job only checks out the base branch (github.event.pull_request.base.ref) and never executes code from the PR head.github.event.pull_request.*fields used by the workflow remain available.Note
pull_request_targetuses the workflow file from the default branch, so this takes effect only after merge. The already-failed release for thefix/key-label-op03n03dPR must be re-run/handled manually.