🦋 Changeset detected

Latest commit: ab95248

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

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

✅ All changesets look good

Both are properly exported. The implementation looks solid. Let me do a final check on whether there are any issues I might have missed:

1. Logic: The stage-and-rename pattern is a well-known atomic directory deployment technique.
2. Error handling: The catch block correctly cleans up the staging directory.
3. copyDirectorySync: Uses readdirSync/statSync/readFileSync which work through Yarn PnP hooks, unlike cpSync.
4. Test: Properly uses { expect } from test context, validates both the service configuration and that files actually exist on disk.
5. Cleanup: The #tmpPath is cleaned up on Miniflare dispose, which will remove the materialized explorer UI.
6. Changeset: Correctly scoped to miniflare as a patch.

The PR is clean. The approach is well-reasoned (stage + atomic rename, manual copy for PnP compatibility), the error handling is correct, and the test covers the key behavior.

LGTM

github run

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

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

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

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

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

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

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

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

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

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

commit: ab95248

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

I have tested that this works in the original repo which triggered the report and repro, and it also works in a half dozen others as well.