🦋 Changeset detected

Latest commit: e812a1b

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

Codeowners approval required for this PR:

• ✅ @cloudflare/cloudchamber
• ✅ @cloudflare/wrangler

I've reviewed the changes thoroughly. There is one issue worth flagging: the error message at line 521 was updated to also check --library-push, but the error text still says "You have to specify either --push or --pull" without mentioning --library-push. This means that passing --library-push alone now bypasses this validation (which is intended behavior based on the test), but the error message for a user who passes none of the flags doesn't mention --library-push as an option. Since --library-push is a hidden flag, this is debatable — a user who knows about --library-push won't get a misleading error because they'll pass the flag. But a user who doesn't know about it would have no idea it exists anyway. So the current error message is acceptable for the hidden flag use case.

The changes are clean, minimal, and correct:

1. The enum value is added properly.
2. The command arg is hidden: true as intended.
3. The permissions array construction mirrors the existing pattern for push/pull.
4. The test covers the new flag.

LGTM

github run

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

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

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

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

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

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

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

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

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

commit: e812a1b

Please add a changeset!

⚠️ Issues found

File: .changeset/plenty-paws-rest.md

Issue: Insufficient changelog description

The body of the changeset reads:

This flag is not available for public use.

This does not meet the quality standard. The README guidelines state the body should explain "the reason for the change and anything notable about the approach" and aim for more than one sentence. A note that the flag is not for public use is not a useful changelog entry on its own — it doesn't describe what the flag does, why it was added, or any relevant context for maintainers or future readers.

If this change is truly internal-only and has no user-facing impact, it may not require a changeset at all (per the README: "Changes that are purely internal refactoring with no user-facing impact" do not need one). If it does warrant a changeset, the description should provide more meaningful context about what the library-push flag does and why it was added.

Overriding the changeset review as this is a feature that is only available for certain internal accounts and no need to document more extensively.