Skip to content

Commit b6a8629

Browse files
dario-piotrowiczdario-piotrowicz
authored
Revert "Version Packages (#14977)" (#15033)
1 parent 6c36427 commit b6a8629

38 files changed

Lines changed: 174 additions & 259 deletions

‎.changeset/ai-search-create-parse-type.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
"wrangler": minor
3+
---
4+
5+
Add `--parse-type` flag to `wrangler ai-search create`
6+
7+
`wrangler ai-search create` now accepts `--parse-type` to control how a website data source discovers URLs. `sitemap` (the default) reads XML sitemaps; `discover` follows links recursively.
8+
9+
Previously the parse type could only be chosen through the interactive wizard, which was skipped whenever `--source` was supplied — so it was impossible to create a `discover` instance from a script.
10+
11+
```sh
12+
wrangler ai-search create my-instance \
13+
--type web-crawler \
14+
--source https://example.com \
15+
--parse-type discover
16+
```
17+
18+
The interactive wizard now offers `Discover` alongside `Sitemap`. `--parse-type` is only valid with `--type web-crawler`; passing it with `--type builtin` or `--type r2` is 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.

‎.changeset/c3-frameworks-update-14974.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
"create-cloudflare": patch
3+
---
4+
5+
Update dependencies of "create-cloudflare"
6+
7+
The following dependency versions have been updated:
8+
9+
| Dependency | From | To |
10+
| ---------- | ------ | ------ |
11+
| sv | 0.16.6 | 0.17.0 |

‎.changeset/c3-frameworks-update-14975.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
"create-cloudflare": patch
3+
---
4+
5+
Update dependencies of "create-cloudflare"
6+
7+
The following dependency versions have been updated:
8+
9+
| Dependency | From | To |
10+
| --------------- | ------ | ------ |
11+
| @angular/create | 22.0.9 | 22.1.2 |

‎.changeset/c3-frameworks-update-14976.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
"create-cloudflare": patch
3+
---
4+
5+
Update dependencies of "create-cloudflare"
6+
7+
The following dependency versions have been updated:
8+
9+
| Dependency | From | To |
10+
| ----------- | ----- | ----- |
11+
| create-vite | 9.1.1 | 9.1.2 |

‎.changeset/container-name-named-env.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
"@cloudflare/workers-utils": patch
3+
---
4+
5+
Use the inherited Worker name when generating container names in named environments
6+
7+
When `containers` is declared inside a named environment and the container has no explicit `name`, the default container name was built from the environment's own `name` field. `name` is inheritable, so an environment that doesn't redeclare it left that value `undefined`, producing the error `Must have either a top level "name" and "containers.class_name" field defined, or have field "containers.name" defined.` even though a top level `name` was set — and, if the error was ignored, a container named `undefined-<class_name>-<env>`.
8+
9+
```jsonc
10+
{
11+
"name": "my-worker",
12+
"env": {
13+
"staging": {
14+
"containers": [{ "class_name": "MyContainer", "image": "./Dockerfile" }],
15+
},
16+
},
17+
}
18+
```
19+
20+
`wrangler deploy --env staging` on the configuration above now generates `my-worker-mycontainer-staging`, matching the documented `worker_name-class_name[-env_name]` default. A `name` declared on the environment still takes precedence over the top level one.

‎.changeset/dependabot-update-14984.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
"miniflare": patch
3+
"wrangler": patch
4+
---
5+
6+
Update dependencies of "miniflare", "wrangler"
7+
8+
The following dependency versions have been updated:
9+
10+
| Dependency | From | To |
11+
| ------------------------- | ------------- | ------------- |
12+
| @cloudflare/workers-types | ^5.20260730.1 | ^5.20260731.1 |
13+
| workerd | 1.20260730.1 | 1.20260731.1 |

‎.changeset/local-explorer-observability-ui-fixes.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
"@cloudflare/vite-plugin": minor
3+
"wrangler": minor
4+
---
5+
6+
Improve the Local Explorer's Observability views
7+
8+
`console.log` messages now render the way the console would (JSON-encoded strings are unwrapped and multi-argument logs are joined), traces and events can be looked up by trace or span id from the search bar, and an event's "View trace" button jumps to the exact invocation that emitted it — even when a trace_id spans several invocations (e.g. a subrequest or self fetch).

‎.changeset/ratelimit-period-scoped-counters.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
"miniflare": patch
3+
---
4+
5+
Fix local rate limiting being disabled entirely when bindings share a `namespace_id` but use different periods
6+
7+
The emulated Ratelimit binding tracked one counter per key per namespace, ignoring the period. Two bindings pointing at the same `namespace_id` with different `simple.period` values 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:
8+
9+
```jsonc
10+
{
11+
"ratelimits": [
12+
{
13+
"name": "BURST",
14+
"namespace_id": "1001",
15+
"simple": { "limit": 20, "period": 10 },
16+
},
17+
{
18+
"name": "SUSTAINED",
19+
"namespace_id": "1001",
20+
"simple": { "limit": 50, "period": 60 },
21+
},
22+
],
23+
}
24+
```
25+
26+
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_id` and a period still share a counter for a given key.

‎.changeset/ratelimit-survive-eviction.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
"miniflare": patch
3+
---
4+
5+
Fix local rate limit counters silently resetting after ~10s of inactivity
6+
7+
The emulated Ratelimit binding kept its counters on the JS heap of an internal Durable Object. `workerd` evicts idle Durable Objects after around 10 seconds, taking the counters with them, so in `wrangler dev` you could hit your Worker, pause to look at something, and find your limit had silently reset part way through the window.
8+
9+
Counters now live in the Durable Object's storage, which survives eviction. They are still cleared by `deleteAllDurableObjects()`, so `reset()` from `@cloudflare/vitest-pool-workers` continues 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 a `wrangler dev` restart within the same window.

‎.changeset/vite-plugin-agent-explorer-hint.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
"@cloudflare/vite-plugin": minor
3+
---
4+
5+
Surface Local Explorer API to headless agents
6+
7+
When a Vite dev or preview server with the Cloudflare plugin is started in a headless AI agent environment, the plugin now prints the Local Explorer API URL and useful resource routes to stdout so agents can discover and call them programmatically.

0 commit comments

Comments
 (0)