Version Packages - #14977
Open
workers-devprod wants to merge 1 commit into
Open
Conversation
workers-devprod
force-pushed
the
changeset-release/main
branch
from
August 2, 2026 10:17
34ad3d5 to
eb67ef9
Compare
Contributor
|
✅ All changesets look good |
workers-devprod
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
August 2, 2026 10:20
5efdda5 to
d3247bf
Compare
@cloudflare/autoconfig
@cloudflare/build-output-utils
@cloudflare/config
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
workers-devprod
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
August 3, 2026 17:11
e73b647 to
ebe0881
Compare
workers-devprod
force-pushed
the
changeset-release/main
branch
from
August 3, 2026 17:35
ebe0881 to
8c963de
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
wrangler@4.119.0
Minor Changes
#14952
20470faThanks @nelsonjsduarte! - Add--parse-typeflag towrangler ai-search createwrangler ai-search createnow accepts--parse-typeto control how a website data source discovers URLs.sitemap(the default) reads XML sitemaps;discoverfollows links recursively.Previously the parse type could only be chosen through the interactive wizard, which was skipped whenever
--sourcewas supplied — so it was impossible to create adiscoverinstance from a script.The interactive wizard now offers
DiscoveralongsideSitemap.--parse-typeis only valid with--type web-crawler; passing it with--type builtinor--type r2is rejected, since the API stores the value for those source types but never reads it. When the flag is omitted in non-interactive mode the field is left unset and the API default (sitemap) applies.Patch Changes
#14984
9c74538Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
Updated dependencies [
9c74538,a88d169,a88d169,daf65f2]:create-cloudflare@2.70.17
Patch Changes
#14974
3dc2ea3Thanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
#14975
1f6844aThanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
#14976
1e1cfc0Thanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
@cloudflare/deploy-helpers@0.6.5
Patch Changes
9c74538,a88d169,a88d169,daf65f2]:miniflare@5.20260731.0-alpha
Patch Changes
#14984
9c74538Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#14968
a88d169Thanks @petebacondarwin! - Fix local rate limiting being disabled entirely when bindings share anamespace_idbut use different periodsThe emulated Ratelimit binding tracked one counter per key per namespace, ignoring the period. Two bindings pointing at the same
namespace_idwith differentsimple.periodvalues therefore overwrote each other's counter on every call — each one seeing a window it did not recognise, and so resetting the count to zero — with the result that neither binding ever limited anything:{ "ratelimits": [ { "name": "BURST", "namespace_id": "1001", "simple": { "limit": 20, "period": 10 } }, { "name": "SUSTAINED", "namespace_id": "1001", "simple": { "limit": 50, "period": 60 } } ] }Counters are now tracked per period, matching production, where a counter is identified by a bucket index and bucket start timestamp that are both derived from the period. Bindings that share a
namespace_idand a period still share a counter for a given key.#14968
a88d169Thanks @petebacondarwin! - Fix local rate limit counters silently resetting after ~10s of inactivityThe emulated Ratelimit binding kept its counters on the JS heap of an internal Durable Object.
workerdevicts idle Durable Objects after around 10 seconds, taking the counters with them, so inwrangler devyou could hit your Worker, pause to look at something, and find your limit had silently reset part way through the window.Counters now live in the Durable Object's storage, which survives eviction. They are still cleared by
deleteAllDurableObjects(), soreset()from@cloudflare/vitest-pool-workerscontinues to reset rate limit state between tests, exactly as it does for KV, R2 and D1. Counters are now also written to the persistence directory, so they survive awrangler devrestart within the same window.#14989
daf65f2Thanks @petebacondarwin! - Surface the full runtime crash report when workerd crashes, and warn when it is restartedWhen workerd crashed, the banner (e.g.
*** std::terminate() called with no exception) was reported without its stack trace, because the stack trace was being filtered out along with the ordinary hex-stack noise workerd emits. The crash was therefore impossible to diagnose. Thestack:line and the missing-$LLVM_SYMBOLIZERnotice that follow a fatal crash banner are now kept, and the whole report is logged aterrorlevel.Miniflare also recovers from workerd crashes by restarting the runtime, but did so silently, which made a crash look like an unexplained dev server restart. It now warns, including a count so that a repeatedly-crashing runtime is distinguishable from a one-off.
@cloudflare/pages-shared@0.13.164
Patch Changes
9c74538,a88d169,a88d169,daf65f2]:@cloudflare/vite-plugin@1.50.1
Patch Changes
20470fa,9c74538,a88d169,a88d169,daf65f2]:@cloudflare/vitest-pool-workers@0.20.2
Patch Changes
20470fa,9c74538,a88d169,a88d169,daf65f2]:@cloudflare/remote-bindings@0.0.7
Patch Changes
9c74538,a88d169,a88d169,daf65f2]:@cloudflare/runtime-types@0.0.9
Patch Changes
9c74538,a88d169,a88d169,daf65f2]: