Skip to content

Commit 88cd089

Browse files
edvilmeCopilot
andauthored
Enable merged-PR release branch preparation (#2006)
## Summary Follow-up to #2003. Adds only `.github/workflows/release-pr-release.yml`; the separate read-only `Release PR / Plan` workflow is unchanged. Keeping the release trigger separate also avoids overlapping the plan-adoption PR. - Handles only `pull_request_target: closed` events targeting `main`, and runs only when the PR was merged. Closing an unmerged PR does not run the release job. - Calls `microsoft/vscode-python-ci/actions/release-pr@4e0c4335bbf6b1a274673e22d9c39cd7efb93ccf` with `mode: release` and the default `release/` prefix. Only this dedicated job receives `contents: write`; no custom token or additional checkout is added. - Revalidates the exact merged change and the PR creator's current write/maintain/admin permission. Only root-`package.json`-only, top-level-version-only valid bumps qualify. Ordinary PRs skip successfully. Creates `release/<calculated-stable-version>` without pushing to `main` or updating an existing release branch; retries fail if the branch already exists. - Uses the trusted target-branch workflow and pinned action; no checked-out PR scripts or hooks are executed. Reports either the created branch/stable version or that no release candidate was found. ## Activation and prerequisites **Merging this PR enables release-branch creation on subsequent qualifying merges. The existing Azure stable pipeline matches `release/*` and defaults `publishExtension` to `true`, so branch creation can publish an extension.** This does not change Azure YAML, publishing approvals, credentials, or branch protection. - Plan prerequisite #2003 is merged. - Before approving activation, configure/confirm `Release PR / Plan` as a required check and confirm the Actions bot can create `release/*` refs. - Confirm the intended Azure pipeline is enabled, its UI trigger overrides match the checked-in YAML, and publishing permissions/approvals are ready. Only checked-in configuration was inspected; live publishing was not exercised. - Prefer observing the [Black Formatter pilot](microsoft/vscode-black-formatter#841) before approving the remaining repositories. No release branches were created as part of this PR. ## Validation - Prettier, whitespace checks, and actionlint v1.7.7 pass for the new workflow. - Local workflow contract checks cover the main/closed event filter, merged-only guard, dedicated write permission, reviewed action pin, and single-file scope. Bash syntax and both job-summary outcomes pass. - The exact pinned shared action passes all 22 tests: 15 release-action tests and 7 version-action tests, including authorization/API failures, unchanged-version skips, stable serialization, and existing-branch rejection. - The release workflow cannot be exercised on an open PR: it uses the trusted target-branch workflow after merge. No live release/publish smoke test is claimed. Where the plan check is already present on `main`, this workflow-only PR should pass as not applicable. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 956d3afd-ae0b-486c-a60c-3a6276c23213
1 parent 6454420 commit 88cd089

1 file changed

Lines changed: 34 additions & 0 deletions

File tree

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
name: Release PR Release
2+
3+
on:
4+
pull_request_target:
5+
branches: [main]
6+
types: [closed]
7+
8+
permissions:
9+
contents: read
10+
11+
jobs:
12+
release:
13+
name: Release PR / Release
14+
if: github.event.pull_request.merged == true
15+
runs-on: ubuntu-latest
16+
permissions:
17+
contents: write
18+
steps:
19+
- name: Prepare release branch
20+
id: release
21+
uses: microsoft/vscode-python-ci/actions/release-pr@4e0c4335bbf6b1a274673e22d9c39cd7efb93ccf
22+
with:
23+
mode: release
24+
- name: Summarize release branch
25+
env:
26+
VERSION: ${{ steps.release.outputs.version }}
27+
BRANCH: ${{ steps.release.outputs.branch }}
28+
shell: bash
29+
run: |
30+
if [[ -n "$VERSION" ]]; then
31+
echo "Created release branch: $BRANCH (stable version $VERSION)." >> "$GITHUB_STEP_SUMMARY"
32+
else
33+
echo "Not a release candidate; no branch created." >> "$GITHUB_STEP_SUMMARY"
34+
fi

0 commit comments

Comments
 (0)