Repository navigation
Use pull_request for release automation - #2031
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 — Rich Chiodo (@rchiodo) 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: C:\Users\rchiodo\AppData\Local\Programs\Podman\podman.EXE --connection pyrx-automation failed: stderr: Error: unable to start container "3efa871d0b120ead4b502339ba30dfe3036a1a0bc54f1d537714afaf430d1b20": crun: open `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found Test runs: none recorded. |
Rich Chiodo (rchiodo)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
Stella Huang (StellaHuang95)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
Bill Schnurr (bschnurr)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
e2685bd
into
main
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
docs/releasing.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: Prettier, whitespace, and exact scoped-diff checks passed. The release workflow is unchanged by this documentation follow-up.