From eac5ba4163eba3012c149c309f4be95a6c189a57 Mon Sep 17 00:00:00 2001 From: Eduardo Villalpando Mello Date: Tue, 17 Nov 2026 15:09:16 -0800 Subject: [PATCH 1/2] Use pull_request for release automation 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 --- .github/workflows/release-pr-release.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release-pr-release.yml b/.github/workflows/release-pr-release.yml index 4724208d7d5c..002145ab6d40 100644 --- a/.github/workflows/release-pr-release.yml +++ b/.github/workflows/release-pr-release.yml @@ -1,7 +1,7 @@ name: Release PR Release on: - pull_request_target: + pull_request: branches: [main] types: [closed] @@ -11,7 +11,7 @@ permissions: jobs: release: name: Release PR / Release - if: github.event.pull_request.merged == true + if: github.event.pull_request.merged == true && github.event.pull_request.head.repo.id == github.event.pull_request.base.repo.id runs-on: ubuntu-latest permissions: contents: write From 8786c5a4c597a74531227db294ed421b88aeaa68 Mon Sep 17 00:00:00 2001 From: Eduardo Villalpando Mello Date: Tue, 17 Nov 2026 15:21:00 -0800 Subject: [PATCH 2/2] Document same-repository release PR requirement Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 956d3afd-ae0b-486c-a60c-3a6276c23213 --- .github/release_plan.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/release_plan.md b/.github/release_plan.md index 45bb33cd9b3b..e96f2452532a 100644 --- a/.github/release_plan.md +++ b/.github/release_plan.md @@ -1,4 +1,10 @@ ### General Notes + +Release PRs must originate from a branch in the upstream +`microsoft/vscode-python` repository, not a fork. The PR's head and base +repositories must match. **Release PR / Release** skips fork-originated PRs, +even when opened by a maintainer. + All dates should align with VS Code's [iteration](https://github.com/microsoft/vscode/labels/iteration-plan) and [endgame](https://github.com/microsoft/vscode/labels/endgame-plan) plans. Feature freeze is Monday @ 17:00 America/Vancouver, XXX XX. At that point, commits to `main` should only be in response to bugs found during endgame testing until the release candidate is ready.