🦋 Changeset detected

Latest commit: e3d301d

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

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

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

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

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

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

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

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

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

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

commit: 103460e

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Please could you add a changeset. It can just describe the change very briefly.

This is a one-line change for a test to enable a feature in another repo that won't be available externally for now. I can add a change set, but wouldn't this be the kind of PR that doesn't require one?

Please could you add a changeset. It can just describe the change very briefly.

This is a one-line change for a test to enable a feature in another repo that won't be available externally for now. I can add a change set, but wouldn't this be the kind of PR that doesn't require one?

What do you mean about it being a "change for a test"? CREATE_PROXY_PROTOTYPE_CLASS_HELPER_SCRIPT isn't only used for testing, or am I misunderstanding?

We generally add changesets for any change that should trigger a version bump and release.

Right, the change here isn't test-only, that's case with the follow-up change in #12802. Corrected the PR and commit title and added a change set.

⚠️ Issues found

File: .changeset/ten-dancers-know.md

1. Missing body: The changeset contains only a title with no body. The README requires "one or more paragraphs explaining the reason for the change and anything notable about the approach." A description like "Add support for worker connect handler in miniflare" tells users what changed but not why it was needed, how it works, or what users can do with it.

2. Version type (minor consideration): The description says "Add support for..." which indicates new functionality. Per the README, new features should be minor. If this is adding a new capability to miniflare (e.g., implementing a previously unsupported Workers runtime handler), it likely warrants minor rather than patch. Please confirm whether this is a bug fix/alignment with existing behavior (patch) or genuinely new functionality (minor).

⚠️ Issues found

File: .changeset/ten-dancers-know.md

1. Missing body: The changeset contains only a title with no body. The README requires "one or more paragraphs explaining the reason for the change and anything notable about the approach." A description like "Add support for worker connect handler in miniflare" tells users what changed but not why it was needed, how it works, or what users can do with it.
2. Version type (minor consideration): The description says "Add support for..." which indicates new functionality. Per the README, new features should be minor. If this is adding a new capability to miniflare (e.g., implementing a previously unsupported Workers runtime handler), it likely warrants minor rather than patch. Please confirm whether this is a bug fix/alignment with existing behavior (patch) or genuinely new functionality (minor).

• missing body? There is precedent for having a one-line change set description, see e.g .changeset/late-humans-win.md.
• This does not introduce any new user-facing functionality since connect() will be behind the "experimental" compat flag, so patch should be appropriate.