[fixtures] Skip dev-registry tests on Windows

[petebacondarwin]

The fixtures/dev-registry suite is consistently failing on Windows in CI and is blocking unrelated work. This skips it on Windows as a temporary measure to unblock the pipeline, while keeping full coverage on macOS and Linux.

The fixture has five top-level describe blocks, so rather than wrapping the whole file in a platform conditional (as fixtures/interactive-dev-tests/tests/index.test.ts does), this aliases the vitest import and derives a locally-skipped describe:

const describe = baseDescribe.skipIf(process.platform === "win32");

That covers all five blocks in a five-line diff with no re-indentation, which keeps the eventual revert trivial.

Verification:

• All 27 tests live inside those five describe blocks — no top-level it/test escapes the skip.
• Forcing the condition to true locally reports 27 skipped and exits 0, so Windows goes green rather than erroring on an empty test file.
• With the real check in place, vitest list still enumerates all 27 tests on macOS.
• oxfmt --check and check:type both pass. Lint is not applicable — .oxlintrc.jsonc ignores fixtures/**.

Note that this is a blanket file-level skip, so any new Windows regression in the dev registry will also go unnoticed on that platform, not just the current failure. The TODO marks it as temporary but nothing enforces cleanup, so this should be reverted once the root cause is fixed.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because: this is a test-only change that skips an existing suite on one platform. There is no product behaviour change to cover. The skip itself was verified locally as described above.
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: this only affects which platforms an internal test fixture runs on, with no user-facing impact.

A picture of a cute animal (not mandatory, but encouraged)

[changeset-bot]

⚠️ No Changeset found

Latest commit: a637a3b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ask-bonk]

All five describe blocks are top-level and use the local aliased describe. There are no top-level it/test calls escaping the skip. Let me verify the approach matches the referenced pattern and confirm skipIf returns a properly-typed describe.

The change is correct:

• baseDescribe.skipIf(...) is a valid vitest API returning a describe-compatible function
• The local const describe shadows the import within the module scope, and all five describe blocks are declared after line 24, so they resolve to the shadowed const (no TDZ issue since they execute after the const initialization)
• All 27 tests are nested inside the five blocks
• On non-Windows the condition is false, so tests run normally

The author's own PR description already thoroughly documents the tradeoffs (blanket skip masks future Windows regressions, TODO not enforced). These are acknowledged design decisions for a temporary unblock, not bugs. The implementation is correct and minimal.

No logic bugs, security issues, backward-compat violations, or incorrect API behavior found.

LGTM

github run

[dario-piotrowicz]

Thanks @petebacondarwin 🙏

[workers-devprod]

Codeowners reviews satisfied

[pkg-pr-new]

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@15018

@cloudflare/build-output-utils

npm i https://pkg.pr.new/@cloudflare/build-output-utils@15018

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@15018

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@15018

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@15018

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@15018

miniflare

npm i https://pkg.pr.new/miniflare@15018

@cloudflare/pages-functions

npm i https://pkg.pr.new/@cloudflare/pages-functions@15018

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@15018

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@15018

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@15018

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@15018

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@15018

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@15018

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@15018

wrangler

npm i https://pkg.pr.new/wrangler@15018

commit: a637a3b

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

[petebacondarwin]

Let's merge this one for today, so that we can get the release out and unblock other PRs.
In the meantime we can look at #15017 as a possible mitigation.