Repository navigation
Use pull_request for release automation - #26301
Open
Eduardo Villalpando Mello (edvilme) wants to merge 2 commits into
Open
Eduardo Villalpando Mello (edvilme) wants to merge 2 commits into
Eduardo Villalpando Mello (edvilme) wants to merge 2 commits into
Conversation
Require merged same-repository PRs while preserving existing release safeguards. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 956d3afd-ae0b-486c-a60c-3a6276c23213
|
🔒 Automated review in progress — Stella Huang (@StellaHuang95) is auto-reviewing this PR. |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 956d3afd-ae0b-486c-a60c-3a6276c23213
|
Reviewed commit: Result: 🔴 Verification detailsVerification: Automated verification is best effort. The PR author remains responsible for testing. Summary: [unavailable] Container verification could not start and local execution was not authorized for this PR HEAD: Podman CLI is not installed or is not on PATH. Test runs: none recorded. |
Bill Schnurr (bschnurr)
approved these changes
Nov 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
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.
Summary
pull_request_targetwithpull_requestin.github/workflows/release-pr-release.yml, retaining themainbranch filter andclosedactivity type.contents: write, pinned shared action, release mode, and existing version-only/author-authorization safeguards. The read-only Release PR / Plan workflow is unchanged.Same-repository release PRs retain the intended release-branch creation behavior. Fork-originated PRs now explicitly skip the release job, including forks opened by maintainers. No new secrets or shared-action changes are needed.
This removes the privileged event rather than requiring a
pull_request_targetpolicy exception.Validation
git diff --checkpassed.@actions/expressionsevaluator passed five condition cases per repository (40 total): merged/unmerged same-repository PRs, merged/unmerged forks, and a deleted fork repository.GitHub-hosted closed-event behavior, the effective write token, and actual release-branch creation still require a controlled post-merge same-repository release PR. No release or publishing pipeline was manually triggered.
Release documentation
Updated
.github/release_plan.md: release PRs must originate from a branch in the upstream repository, not a fork. Head and base repositories must match; fork-originated PRs are skipped even when opened by a maintainer. Release-agent trigger references now usepull_requestwhere applicable.Documentation validation: whitespace, exact scoped-diff checks, and Prettier on the added paragraph passed. Full-file Prettier also fails on the original release plan in HEAD; unrelated legacy formatting is unchanged. The release workflow is unchanged by this documentation follow-up.