ci: run Windows jobs on Namespace runners by fengmk2 · Pull Request #2083 · voidzero-dev/vite-plus

fengmk2 · 2026-07-07T11:47:57Z

Run the Windows CI and release jobs on Namespace runners, matching how Linux and macOS already do, except for the handful of jobs that depend on GitHub-hosted Windows behavior.

What changed

Swap windows-latest -> namespace-profile-windows-4c-8g (4 vCPU / 8 GB) for the Windows jobs in ci.yml, e2e-test.yml, test-standalone-install.yml, and reusable-release-build.yml (x86_64 native + aarch64 cross-compiled on the amd64 host). Windows-specific if: conditions move from matrix.os == 'windows-latest' to the label-independent runner.os == 'Windows', and e2e-test's exclude rules follow the new label.

Prerequisite

The windows-4c-8g profile (Windows Server 2022, amd64) must exist in the Namespace dashboard, otherwise these jobs queue instead of running.

Namespace service-account accommodation

Namespace's Windows runners execute jobs under a Session-0 service account whose real user profile is C:\Windows\system32\config\systemprofile, not %USERPROFILE% (GitHub-hosted windows-latest runs as an interactive user where the two match). For the install jobs that only check shim placement, pinning VP_HOME=%USERPROFILE%\.vite-plus is enough, so test-install-ps1-v5/-v76 and test-vp-setup-exe stay on Namespace. The install version pin was also dropped so the scripts install latest instead of the stale alpha dist-tag.

Kept on GitHub-hosted windows-latest (with inline rationale comments)

windows-11-arm install test: Namespace has no Windows ARM64.
cli-snapshot-test-windows: a PTY snapshot suite. The runner opens a pseudo-console (ConPTY) and spawns vp into it; under the Session-0 service account (no interactive console) that spawn blocks, vp never launches, and every case times out at 60s. Verified via a temporary debug workflow: the vp process count stays 0 for the full 60s.
test-install-ps1 (plain): runs vp env doctor under bash set -e; on the service account vp resolves the systemprofile home even with VP_HOME set, so doctor's PATH check fails.

reusable-release-build.yml still needs the MSVC toolchain (VS Build Tools + Windows SDK) present on the Namespace image; watch that job's first green run.

Runner speed (before vs after)

The Windows run-only jobs are roughly 2x faster on Namespace than on windows-latest. Same job content (they download prebuilt binaries and run tests), only runs-on changed, so this is purely the runner. Sampled across two CI run pairs (windows-latest on main vs Namespace on this PR):

Job (switched to Namespace)	windows-latest	Namespace 4c/8g	Speedup
Test (Windows)	3m01s / 3m34s	1m42s / 1m51s	~46%
CLI E2E test (Windows)	3m59s / 5m07s	2m17s / 2m04s	~50%
CLI snap test 1/3	3m54s / 4m00s	2m08s / 2m09s	~46%
CLI snap test 2/3	4m04s / 6m50s	2m28s / 2m26s	~52%
CLI snap test 3/3	4m47s / 5m03s	2m14s / 2m30s	~52%

Summed, those jobs drop from ~19m45s to ~10m49s of Windows-runner time per run, despite the Namespace shape having less RAM (8 GB vs 16 GB). Not part of this comparison: Build Windows CLI/tests already cross-compile on Namespace Linux (unchanged), and cli-snapshot-test-windows, windows-11-arm, and test-install-ps1 (plain) stay on windows-latest.

netlify · 2026-07-07T11:48:02Z

✅ Deploy Preview for viteplus-preview canceled.

Name	Link
🔨 Latest commit	`c9e4d34`
🔍 Latest deploy log	https://app.netlify.com/projects/viteplus-preview/deploys/6a4e74f07935cc000898fc7a

fengmk2 · 2026-07-07T11:48:11Z

ci: run Windows jobs on Namespace runners #2083 👈 (View in Graphite)
main

How to use the Graphite Merge Queue

Add the label auto-merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

_{An organization admin has enabled the Graphite Merge Queue in this repository.} _{Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.}

This stack of pull requests is managed by Graphite. Learn more about stacking.

github-actions · 2026-07-08T09:45:20Z

Registry bridge build (`e833057`)

This commit build is published to the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):

Package	Version
`vite-plus`	`0.0.0-commit.e833057f2e9462c421d346ca2a4d9356743f90b1`
`@voidzero-dev/vite-plus-core`	`0.0.0-commit.e833057f2e9462c421d346ca2a4d9356743f90b1`

Install the Vite+ CLI built from this commit, then migrate a project:

# macOS / Linux
curl -fsSL https://vite.plus | VP_PR_VERSION=2083 bash

# Windows (PowerShell)
$env:VP_PR_VERSION="2083"; irm https://vite.plus/ps1 | iex

After installing, upgrade the current project's vite-plus to this test build with:

vp migrate

Or point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:

Package manager	Registry config
npm / pnpm / Bun	`.npmrc`: `registry=https://registry-bridge.viteplus.dev/`
Yarn (v2+)	`.yarnrc.yml`: `npmRegistryServer: "https://registry-bridge.viteplus.dev/"`

Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry):

{
  "devDependencies": {
    "vite-plus": "0.0.0-commit.e833057f2e9462c421d346ca2a4d9356743f90b1",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.e833057f2e9462c421d346ca2a4d9356743f90b1"
  }
}

github-actions · 2026-07-08T09:46:35Z

🐳 Docker preview image

Built from this PR's registry bridge build:

Image	Compressed size
`ghcr.io/voidzero-dev/vite-plus:pr-2083`	240MB

# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-2083 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2083

Quick check:

docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2083 vp --version

See docs/guide/docker.md for usage.

fengmk2 · 2026-07-08T15:38:16Z

@codex review

Swap windows-latest -> namespace-profile-windows-x64-default for the movable Windows jobs in ci.yml, e2e-test.yml, and test-standalone-install.yml, matching how Linux and macOS already use Namespace profiles. Windows-specific if: conditions move from matrix.os == 'windows-latest' to the label-independent runner.os == 'Windows', and e2e-test's exclude rules follow the new label. Left on GitHub-hosted runners: the windows-11-arm install test (Namespace has no Windows ARM64) and reusable-release-build.yml (ships MSVC-native user binaries). Requires a namespace-profile-windows-x64-default profile (Windows Server 2022, amd64) in the Namespace dashboard.

Switch the Windows runs-on labels from a namespace-profile-* label to the inline nscloud-windows-2022-amd64-8x16 form. Inline labels need no Namespace dashboard profile (they work as long as the repo is connected to Namespace), so this drops the one-time dashboard setup. Shape 8x16 (8 vCPU / 16 GB) matches windows-latest RAM and doubles the cores.

Switch the Windows runs-on labels to the dashboard profile namespace-profile-windows-4c-8g (4 vCPU / 8 GB), matching the namespace-profile-* style already used for Linux and macOS. Requires that profile to exist in the Namespace dashboard.

Move reusable-release-build.yml's two Windows targets (x86_64 native, aarch64 cross-compiled on the amd64 host) from windows-latest to namespace-profile-windows-4c-8g. The release build needs the native MSVC toolchain (VS Build Tools + Windows SDK) on the runner image.

…ere tests check Namespace's Windows runners execute jobs under a service account whose real user profile (C:\Windows\system32\config\systemprofile) differs from %USERPROFILE% (C:\Users\runneradmin). vp resolves its home from the OS profile, so install.ps1 placed vp.exe under %USERPROFILE%\.vite-plus while 'vp env setup' wrote node/npm/npx shims into the systemprofile home, and the assertions checking %USERPROFILE%\.vite-plus\bin failed with 'Shim not found'. vp-setup.exe and the snapshot suite's VP_SNAP_* paths hit the same split. Pin VP_HOME to %USERPROFILE%\.vite-plus in the five affected jobs (test-install-ps1-v5/-v76/plain, test-vp-setup-exe, cli-snapshot-test-windows) so the install, generated shims, and assertions share one location. Also switch the PowerShell 7.6 job's 'dotnet tool install' from --global (resolves under the systemprofile) to an explicit --tool-path.

The standalone-install tests pinned VP_VERSION to the alpha dist-tag, which is stale (0.1.21-alpha.7, published 2026-05-13) and predates the VP_HOME fix in #2029 (2026-07-05). On Namespace's service-account Windows runners that old binary's 'vp env doctor' ignores VP_HOME and resolves the systemprofile home, failing the plain test-install-ps1 job. Drop VP_VERSION entirely so install.ps1/install.sh/vp-setup.exe default to latest (a build that contains #2029), which also lets the tests track releases instead of a hardcoded version.

…pace Reproduces cli-snapshot-test-windows's 60s hangs on namespace-profile-windows-4c-8g with two instrumented probes: (1) bare vp --help under an isolated empty VP_HOME + VITE_LOG=trace with a hard 30s wait and a CPU sampler (empty VP_HOME is the variable the passing cli-e2e-test job doesn't exercise; distinguishes a self-exec spin from a blocked prompt), and (2) the single help::global case through the PTY runner with --no-capture. Trigger via push to this file or workflow_dispatch. Remove before merge.

Probe 1 (bare vp --help, empty VP_HOME, no PTY) exits 0 with full help; Probe 2 (same case via the PTY runner) hangs 60s with ZERO output, before vp's first trace line, so vp wedges at ConPTY startup. Rework Probe 2 to launch nextest in the background and sample vp/node process count + CPU in the foreground (the earlier '&'-backgrounded sampler output was never captured), to distinguish a self-exec spin (rising CPU / many vp procs) from a blocked ConPTY read (flat CPU, one vp).

Two Windows jobs cannot run on Namespace Session-0 service-account runners and move back to windows-latest, with code comments explaining why. cli-snapshot-test-windows is a PTY snapshot suite: the runner opens a ConPTY and spawns vp into it; under the Session-0 service account (no interactive console) that spawn blocks, vp never launches, and every case times out at 60s (verified: the vp process count stays 0 for the full 60s). test-install-ps1 (plain) runs vp env doctor under bash set -e; on the service account the installed vp resolves the systemprofile home rather than %USERPROFILE% even with VP_HOME set, so the doctor PATH check fails. The other install jobs stay on Namespace because they do not run doctor under set -e. Also removes the temporary debug-snapshot-hang.yml workflow used to diagnose the ConPTY hang.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 47ae5ffcb6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

setup-dev-drive v4 mounts its ReFS VHD on namespace-profile-windows-4c-8g and all three cli-snap-test Windows shards pass with the step succeeding, so the shards stay on Namespace. Documents this inline in response to review feedback.

fengmk2 · 2026-07-08T16:03:59Z

@codex review

chatgpt-codex-connector · 2026-07-08T16:08:47Z

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: c9e4d34643

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@liangmiQwQ

) Release vite-plus v0.2.5: Cleaner environments and more reliable workflows. This release adds cleanup and package version commands, supports TypeScript 7 declaration generation, reduces the standalone binary size, and hardens task tracking, CLI output, package-manager routing, Docker workflows, and project scaffolding. ### Highlights - Add `vp env clean` to remove unused managed Node.js runtimes and package-manager caches ([#2003](#2003)), by @liangmiQwQ - Add `vp pm version`, forwarding native version commands to npm, pnpm, Yarn, and Bun ([#2127](#2127)), by @jong-kyung - Add TypeScript 7 support to declaration generation and generated library projects with tsdown `0.22.7` ([#2104](#2104), [#2168](#2168)), by @wan9chi - Improve automatic task input tracking for Bun on macOS, Linux containers with constrained `/dev/shm`, and Windows process images, reduce Windows backing-file allocation, and clarify task wait failures ([vite-task#515](voidzero-dev/vite-task#515), [vite-task#518](voidzero-dev/vite-task#518), [vite-task#523](voidzero-dev/vite-task#523), [vite-task#524](voidzero-dev/vite-task#524), [vite-task#542](voidzero-dev/vite-task#542), [#2126](#2126), [#2167](#2167)), by @wan9chi - Prevent CLI diagnostics from truncating or panicking when inherited standard output or error is nonblocking ([#2172](#2172), [#2173](#2173)), by @wan9chi ### Fixes & Enhancements - Reduce standalone `vp` binary sizes by about 5% on Linux and macOS and 19% on Windows ([#2043](#2043)), by @fengmk2 - Keep the Docker image non-root by default while allowing passwordless `sudo` for Playwright browser dependencies and system packages ([#2088](#2088)), by @fengmk2 - Ignore `.env` and `.env.*` in generated projects while keeping `.env.example` trackable ([#2095](#2095)), by @forehalo - Create `vp-use.cmd` after the Windows environment bin directory is ready and document its Command Prompt-only usage ([#2128](#2128)), by @liangmiQwQ - Render user-facing process statuses and paths without Rust debug wrappers ([#2130](#2130)), by @liangmiQwQ - Make `vp dedupe` fall back to `yarn install` with a warning on Yarn Classic ([#2139](#2139)), by @jong-kyung - Ensure package-manager child processes, including Bun, can always find the managed Node.js runtime ([#2158](#2158)), by @BlankParticle ### Docs - Update the release-manager post-release guidance ([#2096](#2096)), by @wan9chi - Add Windows to the Namespace sponsor credit ([#2108](#2108)), by @fengmk2 - Document installer and runtime environment variables, registry settings, TLS options, and precedence rules ([#2114](#2114)), by @yukinoshi - Mark shell examples in `CONTRIBUTING.md` as Bash code blocks ([#2159](#2159)), by @BlankParticle ### Chore - Assign prepared release PRs to the workflow actor ([#2094](#2094)), by @wan9chi - Complete the PTY snapshot migration and harden the runner, fixtures, release-version redaction, registry teardown, timeouts, and Linux parallelism ([#2071](#2071), [#2080](#2080), [#2084](#2084), [#2099](#2099), [#2102](#2102), [#2103](#2103), [#2107](#2107), [#2109](#2109), [#2115](#2115), [#2117](#2117), [#2118](#2118), [#2119](#2119), [#2120](#2120), [#2121](#2121), [#2131](#2131), [#2132](#2132), [#2134](#2134), [#2137](#2137), [#2138](#2138), [#2141](#2141), [#2143](#2143), [#2145](#2145), [#2182](#2182)), by @fengmk2 and @wan9chi - Expose Vite+ managed binaries consistently inside snapshot fixtures ([#2110](#2110)), by @liangmiQwQ - Exclude PTY snapshot configuration from Vitest discovery and remove the legacy snapshot infrastructure ([#2135](#2135), [#2146](#2146)), by @jong-kyung - Modernize Windows runners, registry bridge publishing, native size reporting, merge-base comparisons, and package-manager installation CI ([#2083](#2083), [#2100](#2100), [#2105](#2105), [#2106](#2106), [#2112](#2112), [#2133](#2133)), by @fengmk2 - Verify that created monorepo libraries emit declarations in CI ([#2171](#2171)), by @wan9chi ### Bundled Versions | Tool | Version | Source | | --------------- | ------- | ----------------------------------------------------------------------- | | vite | `8.1.4` | [`a477454`](vitejs/vite@a477454) | | rolldown | `1.1.5` | [`f09947a`](rolldown/rolldown@f09947a) | | tsdown | `0.22.7` | [npm](https://npmx.dev/package/tsdown/v/0.22.7) | | vitest | `4.1.10` | [npm](https://npmx.dev/package/vitest/v/4.1.10) | | oxlint | `1.73.0` | [npm](https://npmx.dev/package/oxlint/v/1.73.0) | | oxlint-tsgolint | `0.24.0` | [npm](https://npmx.dev/package/oxlint-tsgolint/v/0.24.0) | | oxfmt | `0.58.0` | [npm](https://npmx.dev/package/oxfmt/v/0.58.0) | ### Upgrade ```bash vp upgrade ``` ### New Contributors Welcome @yukinoshi and @BlankParticle. **Full Changelog**: v0.2.4...v0.2.5 --- Merging this PR will trigger the release workflow. --------- Co-authored-by: voidzero-guard[bot] <278573678+voidzero-guard[bot]@users.noreply.github.com> Co-authored-by: wan9chi <dk4rest@gmail.com>

fengmk2 added the preview-build Publish this PR's commits to the registry bridge as preview builds label Jul 8, 2026

wan9chi approved these changes Jul 8, 2026

View reviewed changes

wan9chi mentioned this pull request Jul 8, 2026

fix(test): support Namespace Windows runner voidzero-dev/vite-task#516

Merged

fengmk2 force-pushed the ci/namespace-windows-runners branch 2 times, most recently from 5c22f67 to 2d352fe Compare July 8, 2026 14:35

fengmk2 added 9 commits July 8, 2026 23:38

fengmk2 force-pushed the ci/namespace-windows-runners branch from 47ae5ff to e833057 Compare July 8, 2026 15:39

chatgpt-codex-connector Bot reviewed Jul 8, 2026

View reviewed changes

Comment thread .github/workflows/ci.yml

Comment thread .github/workflows/test-standalone-install.yml

Comment thread .github/workflows/ci.yml

fengmk2 marked this pull request as ready for review July 8, 2026 16:12

fengmk2 merged commit 63f837b into main Jul 8, 2026
114 checks passed

fengmk2 deleted the ci/namespace-windows-runners branch July 8, 2026 16:22

wan9chi mentioned this pull request Jul 15, 2026

release: v0.2.5: Cleaner environments and more reliable workflows #2180

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

ci: run Windows jobs on Namespace runners#2083

ci: run Windows jobs on Namespace runners#2083
fengmk2 merged 10 commits into
mainfrom
ci/namespace-windows-runners

fengmk2 commented Jul 7, 2026 •

edited

Loading

Uh oh!

netlify Bot commented Jul 7, 2026 •

edited

Loading

Uh oh!

fengmk2 commented Jul 7, 2026

Uh oh!

github-actions Bot commented Jul 8, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jul 8, 2026

Uh oh!

fengmk2 commented Jul 8, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fengmk2 commented Jul 8, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 8, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

fengmk2 commented Jul 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changed

Prerequisite

Namespace service-account accommodation

Kept on GitHub-hosted windows-latest (with inline rationale comments)

Runner speed (before vs after)

Uh oh!

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

Uh oh!

✅ Deploy Preview for viteplus-preview canceled.

Uh oh!

fengmk2 commented Jul 7, 2026

How to use the Graphite Merge Queue

Uh oh!

github-actions Bot commented Jul 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Registry bridge build (e833057)

Uh oh!

github-actions Bot commented Jul 8, 2026

🐳 Docker preview image

Uh oh!

fengmk2 commented Jul 8, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fengmk2 commented Jul 8, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 8, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

fengmk2 commented Jul 7, 2026 •

edited

Loading

netlify Bot commented Jul 7, 2026 •

edited

Loading

github-actions Bot commented Jul 8, 2026 •

edited

Loading

Registry bridge build (`e833057`)