From 907a269a1ce1f451c3d8b3c8dc3f630f8046f319 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 4724208d7..002145ab6 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 30b965c380c0de9d2793e03d1823b12d26bcfba4 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 --- docs/releasing.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/releasing.md b/docs/releasing.md index 81e1a1b02..b44f67193 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -4,6 +4,11 @@ Python Environments uses even minor versions for stable releases and odd minor versions for pre-release development. For example, `1.38.0` is a stable release and `1.39.0` starts the next pre-release cycle. +Release PRs must originate from a branch in the upstream +`microsoft/vscode-python-environments` 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. + ## Prepare the release branch Complete these steps before release day: