chore: setup PR-driven release pipeline by hi-ogawa · Pull Request #10550 · vitest-dev/vitest

hi-ogawa · 2026-06-09T06:00:17Z

Description

Closes Rework release pipeline to be PR-driven #10551

This PR implements the basic idea of #10551. The maintainer guide of the release process is added to CONTRIBUTING.md.

The test flight is done in my fork repo. See

There are some aspects that could be improved later but not included here:

Setup Github App to auto create PR during "prepare publish" workflow dispatch.
- Currently "prepare publish" job only outputs the compare URL for human to create PR manually. This is because even though auto creating PR from in-repo GITHUB_TOKEN won't trigger the actions on the created PR due to Github's chaining action prevention.
Automatically derive npm dist-tags for backport release case in publish-ci.ts script.
- publish-ci.ts currently publishes backport release of npm package as release dist tags. To prevent this, we would need manual fix up for each backport branch like v3 or we should implement automatic way to derive dist-tags.
Rework changelog and github release generation. For example, changelog generation could be moved ahead to "prepare publish" time.

They are put into follow up issue #10560

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
Ideally, include a test that fails without this PR but passes with it.
Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

Run the tests with pnpm test:ci.

Documentation

If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Co-authored-by: Codex <[email protected]>

netlify · 2026-06-09T06:01:31Z

✅ Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	`57848fd`
🔍 Latest deploy log	https://app.netlify.com/projects/vitest-dev/deploys/6a2bd0c14c6ceb0008d44876
😎 Deploy Preview	https://deploy-preview-10550--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Co-authored-by: Codex <[email protected]>

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

Co-authored-by: Codex <[email protected]>

Copilot

Pull request overview

Copilot reviewed 8 out of 9 changed files in this pull request and generated 4 comments.

Files not reviewed (1)

pnpm-lock.yaml: Generated file

Co-authored-by: Copilot Autofix powered by AI <[email protected]>

Co-authored-by: Codex <[email protected]>

…into poc/pr-driven-release-pipeline

sheremet-va · 2026-06-12T09:41:01Z

We would also need to backport this to v4 and v3, right? Because the release workflow needs to be identical

hi-ogawa · 2026-06-12T09:41:12Z

Did local dry run. So many warnings but looks good:

$ RELEASE_VERSION=5.0.0-beta.5 pnpm release
[WARN] The "$" version reference syntax in overrides is deprecated (used by: @types/node, rollup, vite). Define the version in a catalog and reference it with the "catalog:" protocol instead. See https://pnpm.io/catalogs
[WARN] The "$" version reference syntax in overrides is deprecated (used by: @types/node, rollup, vite). Define the version in a catalog and reference it with the "catalog:" protocol instead. See https://pnpm.io/catalogs
Scope: all 42 workspace projects
[WARN] There are cyclic workspace dependencies: /home/hiroshi/code/others/vitest-release-pipeline-poc/packages/browser, /home/hiroshi/code/others/vitest-release-pipeline-poc/packages/vitest, /home/hiroshi/code/others/vitest-release-pipeline-poc/packages/browser-playwright
✓ Lockfile passes supply-chain policies (verified 7m ago)
Lockfile is up to date, resolution step is skipped
Packages: +20
++++++++++++++++++++
Progress: resolved 20, reused 20, downloaded 0, added 20, done
Done in 1.3s using pnpm v11.6.0
$ tsx scripts/release.ts
Bumping versions in packages: package.json, packages/browser/package.json, packages/browser-playwright/package.json, packages/browser-webdriverio/package.json, packages/coverage-istanbul/package.json, packages/coverage-v8/package.json, packages/expect/package.json, packages/pretty-format/package.json, packages/snapshot/package.json, packages/browser-preview/package.json, packages/spy/package.json, packages/ui/package.json, packages/mocker/package.json, packages/utils/package.json, packages/web-worker/package.json, packages/vitest/package.json

$  VITE_TEST_WATCHER_DEBUG=false PUBLISH_DRY_RUN=true PUBLISH_BRANCH=main pnpm publish-ci 5.0.0-beta.5
[WARN] The "$" version reference syntax in overrides is deprecated (used by: @types/node, rollup, vite). Define the version in a catalog and reference it with the "catalog:" protocol instead. See https://pnpm.io/catalogs
[WARN] The "$" version reference syntax in overrides is deprecated (used by: @types/node, rollup, vite). Define the version in a catalog and reference it with the "catalog:" protocol instead. See https://pnpm.io/catalogs
Scope: all 42 workspace projects
[WARN] There are cyclic workspace dependencies: /home/hiroshi/code/others/vitest-release-pipeline-poc/packages/browser, /home/hiroshi/code/others/vitest-release-pipeline-poc/packages/vitest, /home/hiroshi/code/others/vitest-release-pipeline-poc/packages/browser-playwright
✓ Lockfile passes supply-chain policies (verified 7m ago)
Lockfile is up to date, resolution step is skipped
Packages: +20
++++++++++++++++++++
Progress: resolved 20, reused 20, downloaded 0, added 20, done
Done in 1.2s using pnpm v11.6.0
$ tsx scripts/publish-ci.ts 5.0.0-beta.5
== DRY RUN ==
Staging version '5.0.0-beta.5' with tag 'beta'
[WARN] The "$" version reference syntax in overrides is deprecated (used by: @types/node, rollup, vite). Define the version in a catalog and reference it with the "catalog:" protocol instead. See https://pnpm.io/catalogs
📦 @vitest/[email protected] → https://registry.npmjs.org/
[WARN] Skip staging @vitest/[email protected] (dry run)
📦 @vitest/[email protected] → https://registry.npmjs.org/
[WARN] Skip staging @vitest/[email protected] (dry run)
📦 @vitest/[email protected] → https://registry.npmjs.org/
[WARN] Skip staging @vitest/[email protected] (dry run)
📦 @vitest/[email protected] → https://registry.npmjs.org/
[WARN] Skip staging @vitest/[email protected] (dry run)
📦 @vitest/[email protected] → https://registry.npmjs.org/
[WARN] 10 other warnings
📦 @vitest/[email protected] → https://registry.npmjs.org/
📦 @vitest/[email protected] → https://registry.npmjs.org/
📦 [email protected] → https://registry.npmjs.org/
📦 @vitest/[email protected] → https://registry.npmjs.org/
📦 @vitest/[email protected] → https://registry.npmjs.org/
📦 @vitest/[email protected] → https://registry.npmjs.org/
📦 @vitest/[email protected] → https://registry.npmjs.org/
📦 @vitest/[email protected] → https://registry.npmjs.org/
📦 @vitest/[email protected] → https://registry.npmjs.org/
📦 @vitest/[email protected] → https://registry.npmjs.org/
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)
[WARN] 11 other warningseta.5 (would stage)
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)
+ [email protected] (would stage)
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)
+ @vitest/[email protected] (would stage)

hi-ogawa · 2026-06-12T09:42:58Z

We would also need to backport this to v4 and v3, right? Because the release workflow needs to be identical

Yes, I'll backport it. Slightly scary updating pnpm there but we'll see.

chore: add PR-driven release pipeline POC

3661379

Co-authored-by: Codex <[email protected]>

hi-ogawa mentioned this pull request Jun 9, 2026

Rework release pipeline to be PR-driven #10551

Closed

github-advanced-security AI found potential problems Jun 9, 2026

View reviewed changes

Comment thread .github/workflows/prepare-publish.yml Fixed

Comment thread .github/workflows/prepare-publish.yml Fixed

docs: explain release detection job split

f466995

Co-authored-by: Codex <[email protected]>

hi-ogawa changed the title ~~chore: add PR-driven release pipeline~~ chore: setup PR-driven release pipeline Jun 9, 2026

hi-ogawa and others added 13 commits June 9, 2026 15:17

nit

fcc1607

nit

5638d0e

refactor: consolidate release preparation helper

280c8f2

Co-authored-by: Codex <[email protected]>

refactor: simplify release preparation POC

db8c22d

Co-authored-by: Codex <[email protected]>

nit

76c8959

nit

1cbb233

nit

3ea79fa

refactor: simplify prepare publish workflow

c200951

Co-authored-by: Codex <[email protected]>

nit

54bd965

refactor: streamline prepare publish branch step

02a9dd6

Co-authored-by: Codex <[email protected]>

chore: satisfy zizmor workflow audit

3dcb948

Co-authored-by: Codex <[email protected]>

refactor: inline release commit detection

910086c

Co-authored-by: Codex <[email protected]>

refactor: derive release tag from version

1eb3191

Co-authored-by: Codex <[email protected]>

sheremet-va reviewed Jun 9, 2026

View reviewed changes

Comment thread .github/workflows/publish.yml Outdated

Comment thread .github/workflows/publish.yml Outdated

hi-ogawa and others added 3 commits June 9, 2026 17:11

refactor: fail when release tag exists

36e07d2

Co-authored-by: Codex <[email protected]>

feat: add publish dry run mode

6e6dc6e

Co-authored-by: Codex <[email protected]>

followup todo

10f445a

sheremet-va reviewed Jun 9, 2026

View reviewed changes

Comment thread .github/workflows/publish.yml Outdated

hi-ogawa and others added 6 commits June 9, 2026 17:45

chore: guard release tag before publish

94f2171

Co-authored-by: Codex <[email protected]>

refactor: simplify release commit detection

0df9167

Co-authored-by: Codex <[email protected]>

refactor: split npm install in publish workflow

d6f074a

Co-authored-by: Codex <[email protected]>

docs: simplify release pipeline instructions

cba57c2

Co-authored-by: Codex <[email protected]>

docs: rewrite release process as high-level guide

23e3171

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

docs: polish release process steps

e5ee3bc

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

sheremet-va reviewed Jun 11, 2026

View reviewed changes

Comment thread .github/workflows/publish.yml Outdated

sheremet-va reviewed Jun 11, 2026

View reviewed changes

Comment thread .github/workflows/publish.yml

hi-ogawa and others added 3 commits June 12, 2026 09:44

ci: use slim runner for release detection

87a7708

Co-authored-by: Codex <[email protected]>

fix: handle any pre-release name in getReleaseTag

6761080

chore: add How to test release script locally:

e3f7f9c

hi-ogawa requested review from Copilot and sheremet-va June 12, 2026 01:13

Copilot started reviewing on behalf of hi-ogawa June 12, 2026 01:13 View session

ci: remove unused prepare publish env

dcb1194

Co-authored-by: Codex <[email protected]>

Copilot AI reviewed Jun 12, 2026

View reviewed changes

Comment thread .github/workflows/publish.yml

Comment thread .github/workflows/publish.yml Outdated

Comment thread pnpm-lock.yaml

Comment thread scripts/publish-ci.ts

typo

c35a5ba

Co-authored-by: Copilot Autofix powered by AI <[email protected]>

sheremet-va reviewed Jun 12, 2026

View reviewed changes

Comment thread .github/workflows/publish.yml Outdated

sheremet-va reviewed Jun 12, 2026

View reviewed changes

Comment thread scripts/publish-ci.ts Outdated

sheremet-va reviewed Jun 12, 2026

View reviewed changes

Comment thread .github/workflows/publish.yml Outdated

hi-ogawa commented Jun 12, 2026

View reviewed changes

Comment thread CONTRIBUTING.md

hi-ogawa commented Jun 12, 2026

View reviewed changes

Comment thread package.json

hi-ogawa and others added 2 commits June 12, 2026 18:24

ci: use npm staged publishing

53511e9

Co-authored-by: Codex <[email protected]>

Merge remote-tracking branch 'origin/poc/pr-driven-release-pipeline' …

57848fd

…into poc/pr-driven-release-pipeline

hi-ogawa requested a review from sheremet-va June 12, 2026 09:34

sheremet-va approved these changes Jun 12, 2026

View reviewed changes

hi-ogawa mentioned this pull request Jun 12, 2026

ci: setup PR-driven release pipeline [backport to v4] #10585

Merged

7 tasks

sheremet-va merged commit 3d421d4 into vitest-dev:main Jun 12, 2026
16 of 18 checks passed

hi-ogawa deleted the poc/pr-driven-release-pipeline branch June 13, 2026 06:19

This was referenced Jun 15, 2026

ci: setup PR-driven release pipeline [backport to v3] #10596

Merged

ci: use release app token for tag push #10599

Merged

chore: use catalog protocol in pnpm overrides #10609

Merged

sheremet-va mentioned this pull request Jun 29, 2026

build: update the release workflow vitest-community/vitest-browser-svelte#35

Merged

Uh oh!

Uh oh!

Conversation

hi-ogawa commented Jun 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

Tests

Documentation

Changesets

Uh oh!

Uh oh!

Uh oh!

netlify Bot commented Jun 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for vitest-dev ready!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

sheremet-va commented Jun 12, 2026

Uh oh!

hi-ogawa commented Jun 12, 2026

Uh oh!

hi-ogawa commented Jun 12, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

hi-ogawa commented Jun 9, 2026 •

edited

Loading

netlify Bot commented Jun 9, 2026 •

edited

Loading