Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/release-pr-release.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name: Release PR Release

on:
pull_request_target:
pull_request:
branches: [main]
types: [closed]

Expand All @@ -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
Expand Down
5 changes: 5 additions & 0 deletions docs/releasing.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
Loading