Revert "Version Packages (#7766)"

This reverts commit cc4af98.

Author: edmundhung

.changeset/chilly-kings-retire.md

@@ -0,0 +1,9 @@
+---
+"create-cloudflare": patch
+---
+
+Fix regression in C3's `next` template
+
+[#7676](https://github.com/cloudflare/workers-sdk/pull/7676) switched C3 templates to default to `wrangler.json` instead of `wrangler.toml`. Unfortunately, this unintendedly broke the `next` template, which was still attempting to read `wrangler.toml` specifically. This commit fixes the regression.
+
+Fixes #7770

.changeset/cuddly-pets-smell.md

@@ -0,0 +1,5 @@
+---
+"wrangler": patch
+---
+
+chore(wrangler): use the unenv preset from `@cloudflare/unenv-preset`

.changeset/fifty-flies-visit.md

@@ -0,0 +1,5 @@
+---
+"wrangler": patch
+---
+
+chore: update unenv dependency version

.changeset/honest-spies-prove.md

@@ -0,0 +1,5 @@
+---
+"wrangler": patch
+---
+
+Unwrap the error cause when available to send to Sentry

.changeset/lovely-years-wash.md

@@ -0,0 +1,5 @@
+---
+"@cloudflare/workers-shared": patch
+---
+
+fix: on a 404 from KV, we do not want the asset to stay in cache for the normal 1 year TTL. Instead we want to re-insert with a 60s TTL to revalidate and prevent a bad 404 from persisting.

.changeset/odd-news-invent.md

@@ -0,0 +1,5 @@
+---
+"workers-playground": patch
+---
+
+fix: sends raw request method through the X-CF-HTTP-Method header

.changeset/proud-forks-build.md

@@ -0,0 +1,36 @@
+---
+"wrangler": patch
+---
+
+fix: widen multi-env `vars` types in `wrangler types`
+
+Currently, the type generated for `vars` is a string literal consisting of the value of the variable in the top level environment. If multiple environments
+are specified this wrongly restricts the type, since the variable could contain any of the values from each of the environments.
+
+For example, given a `wrangler.toml` containing the following:
+
+```
+[vars]
+MY_VAR = "dev value"
+
+[env.production.vars]
+MY_VAR = "prod value"
+```
+
+running `wrangler types` would generate:
+
+```ts
+interface Env {
+	MY_VAR: "dev value";
+}
+```
+
+making typescript incorrectly assume that `MY_VAR` is always going to be `"dev value"`
+
+after these changes, the generated interface would instead be:
+
+```ts
+interface Env {
+	MY_VAR: "dev value" | "prod value";
+}
+```

.changeset/smart-lions-suffer.md

@@ -0,0 +1,7 @@
+---
+"wrangler": patch
+---
+
+feat: pull resource names for provisioning from config if provided
+
+Uses `database_name` and `bucket_name` for provisioning if specified. For R2, this only happens if there is not a bucket with that name already. Also respects R2 `jurisdiction` if provided.

.changeset/tough-walls-poke.md

@@ -0,0 +1,5 @@
+---
+"@cloudflare/workers-shared": minor
+---
+
+Adds jaeger tracing for asset-worker.

.changeset/unlucky-timers-sort.md

@@ -0,0 +1,46 @@
+---
+"wrangler": minor
+---
+
+add `--strict-vars` option to `wrangler types`
+
+add a new `--strict-vars` option to `wrangler types` that developers can (by setting the
+flag to `false`) use to disable the default strict/literal types generation for their variables
+
+opting out of strict variables can be useful when developers change often their `vars` values,
+even more so when multiple environments are involved
+
+## Example
+
+With a toml containing:
+
+```toml
+[vars]
+MY_VARIABLE = "production_value"
+MY_NUMBERS = [1, 2, 3]
+
+[env.staging.vars]
+MY_VARIABLE = "staging_value"
+MY_NUMBERS = [7, 8, 9]
+```
+
+the `wrangler types` command would generate the following interface:
+
+```
+interface Env {
+        MY_VARIABLE: "production_value" | "staging_value";
+        MY_NUMBERS: [1,2,3] | [7,8,9];
+}
+```
+
+while `wrangler types --strict-vars=false` would instead generate:
+
+```
+interface Env {
+        MY_VARIABLE: string;
+        MY_NUMBERS: number[];
+}
+```
+
+(allowing the developer to easily change their toml variables without the
+risk of breaking typescript types)