Version Packages

[workers-devprod]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Minor Changes

• #9535 56dc5c4 Thanks @penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the [d] hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring a launch.json file, running wrangler dev, and connecting via VSCode's built-in debugger.

  Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.

@cloudflare/[email protected]

Minor Changes

• #9803 df04528 Thanks @penalosa! - Support Workers Analytics Engine & Rate Limiting bindings

Patch Changes

• Updated dependencies [56dc5c4, 8acaf43, 4309bb3, d11288a]:
  • [email protected]
  • [email protected]

[email protected]

Minor Changes

• #9535 56dc5c4 Thanks @penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the [d] hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring a launch.json file, running wrangler dev, and connecting via VSCode's built-in debugger.

  Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.

• #9810 8acaf43 Thanks @WillTaylorDev! - WC-3626 Pull branch name from WORKERS_CI_BRANCH if exists.

Patch Changes

• #9775 4309bb3 Thanks @vicb! - Cap the number of errors and warnings for bulk KV put to avoid consuming too much memory

• #9799 d11288a Thanks @penalosa! - Better messaging for account owned tokens in wrangler whoami

• Updated dependencies [56dc5c4]:

  • [email protected]

@cloudflare/[email protected]

Patch Changes

• Updated dependencies [56dc5c4]:
  • [email protected]

@cloudflare/[email protected]

Patch Changes

• Updated dependencies [56dc5c4, 8acaf43, 4309bb3, d11288a]:
  • [email protected]
  • [email protected]

@cloudflare/[email protected]

Patch Changes

• #9824 8104705 Thanks @petebacondarwin! - Allow "plain text" images when blocking vulnerable non-image responses

• #9785 07416ba Thanks @matthewdavidrodgers! - Handle next apps hosted at a path other than the root when blocking vulnerable non-image requests

[pkg-pr-new]

create-cloudflare

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

wrangler

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

commit: 10a2f48