Wrangler Changelog

2024-03-14

3.34.2

#5238 a0768bc Thanks @RamIdeas! - fix: versions upload annotations (--message and/or --tag) are now applied correctly to the uploaded Worker Version

3.34.1

Updated dependencies [ 2e50d51]:
- miniflare@3.20240304.2

3.34.0

#5224 03484c2 Thanks @RamIdeas! - feature: Implement wrangler deployments list and wrangler deployments status behind --experimental-gradual-rollouts flag.
#5115 29e8151 Thanks @RamIdeas! - feature: Implement wrangler versions deploy command.
For now, invocations should use the --experimental-gradual-rollouts flag.
Without args, a user will be guided through prompts. If args are specified, they are used as the default values for the prompts. If the --yes flag is specified, the defaults are automatically accepted for a non-interactive flow.
#5208 4730b6c Thanks @RamIdeas! - feature: Implement wrangler versions list and wrangler versions view commands behind the --experimental-gradual-rollouts flag.
#5064 bd935cf Thanks @OilyLime! - feature: Improve create and update logic for hyperdrive to include caching settings

2024-03-12

3.33.0

#4930 2680462 Thanks @rozenmd! - refactor: default wrangler d1 execute and wrangler d1 migrations commands to local mode first, to match wrangler dev
This PR defaults wrangler d1 execute and wrangler d1 migrations commands to use the local development environment provided by wrangler to match the default behaviour in wrangler dev.
BREAKING CHANGE (for a beta feature): wrangler d1 execute and wrangler d1 migrations commands now default --local to true. When running wrangler d1 execute against a remote D1 database, you will need to provide the --remote flag.
#5184 046930e Thanks @nora-soderlund! - fix: change d1 migrations create to use the highest migration number rather than the first non-existing migration number to allow for gaps in the migration files.
Updated dependencies [ 1235d48, 27fb22b]:
- miniflare@3.20240304.1

2024-03-07

3.32.0

#5148 11951f3 Thanks @dom96! - chore: bump workerd to 1.20240304.0
#5148 11951f3 Thanks @dom96! - fix: use python_workers compat flag for Python

#5089 5b85dc9 Thanks @DaniFoldi! - fix: include all currently existing bindings in wrangler types

Add support for Email Send, Vectorize, Hyperdrive, mTLS, Browser Rendering and Workers AI bindings in wrangler types

For example, from the following wrangler.toml setup:

[browser]
binding = "BROWSER"

[ai]
binding = "AI"

[[send_email]]
name = "SEND_EMAIL"

[[vectorize]]
binding = "VECTORIZE"
index_name = "VECTORIZE_NAME"

[[hyperdrive]]
binding = "HYPERDRIVE"
id = "HYPERDRIVE_ID"

[[mtls_certificates]]
binding = "MTLS"
certificate_id = "MTLS_CERTIFICATE_ID"

Previously, nothing would have been included in the generated Environment. Now, the following will be generated:

interface Env {	SEND_EMAIL: SendEmail;	VECTORIZE: VectorizeIndex;	HYPERDRIVE: Hyperdrive;	MTLS: Fetcher;	BROWSER: Fetcher;	AI: Fetcher;
}

Updated dependencies [ 11951f3, 11951f3]:
- miniflare@3.20240304.0

2024-03-05

3.31.0

#5119 b0bd413 Thanks @garrettgu10! - feature: Python support for remote dev
#5118 30694a3 Thanks @garrettgu10! - fix: Including version identifiers in Python requirements.txt will now throw an error
#5132 82a3f94 Thanks @mrbbot! - fix: switch default logging level of unstable_dev() to warn
When running unstable_dev() in its default “test mode”, the logging level was set to none. This meant any Worker startup errors or helpful warnings wouldn’t be shown. This change switches the default to warn. To restore the previous behaviour, include logLevel: "none" in your options object:
```
const worker = await unstable_dev("path/to/script.js", {	logLevel: "none",
});
```
#5128 d27e2a7 Thanks @taylorlee! - fix: Add legacy_env support to experimental versions upload command.
#5087 a5231de Thanks @dario-piotrowicz! - fix: make wrangler types always generate a d.ts file for module workers
Currently if a config file doesn’t define any binding nor module, running wrangler types against such file would not produce a d.ts file.
Producing a d.ts file can however still be beneficial as it would define a correct env interface (even if empty) that can be expanded/referenced by user code (this can be particularly convenient for scaffolding tools that may want to always generate an env interface).
Example: Before wrangler types --env-interface MyEnv run with an empty wrangler.toml file would not generate any file, after these change it would instead generate a file with the following content:
```
interface MyEnv {
}
```
#5138 3dd9089 Thanks @G4brym! - fix: ensure Workers-AI local mode fetcher returns headers to client worker
Updated dependencies [ 42bcc72, 42bcc72]:
- miniflare@3.20240223.1

2024-02-29

3.30.1

#5106 2ed7f32 Thanks @RamIdeas! - fix: automatically drain incoming request bodies
Previously, requests sent to wrangler dev with unconsumed bodies could result in Network connection lost errors. This change attempts to work around the issue by ensuring incoming request bodies are drained if they’re not used. This is a temporary fix whilst we try to address the underlying issue. Whilst we don’t think this change will introduce any other issues, it can be disabled by setting the WRANGLER_DISABLE_REQUEST_BODY_DRAINING=true environment variable. Note this fix is only applied if you’ve enabled Wrangler’s bundling—--no-bundle mode continues to have the previous behaviour.
#5107 65d0399 Thanks @penalosa! - fix: Ensures that switching to remote mode during a dev session (from local mode) will correctly use the right zone. Previously, zone detection happened before the dev session was mounted, and so dev sessions started with local mode would have no zone inferred, and would have failed to start, with an ugly error.
#5107 65d0399 Thanks @penalosa! - fix: Ensure that preview sessions created without a zone don’t switch the host on which to start the preview from the one returned by the API.
#4833 54f6bfc Thanks @admah! - fix: remove extra arguments from wrangler init deprecation message and update recommended c3 version
c3 can now infer the pre-existing type from the presence of the --existing-script flag so we can remove the extra type argument. C3 2.5.0 introduces an auto-update feature that will make sure users get the latest minor version of c3 and prevent problems where older 2.x.x versions get cached by previous runs of wrangler init.

2024-02-27

3.30.0

#4742 c2f3f1e Thanks @benycodes! - feat: allow preserving file names when defining rules for non-js modules
The developer is now able to specify the `preserve_file_names property in wrangler.toml which specifies whether Wrangler will preserve the file names additional modules that are added to the deployment bundle of a Worker.
If not set to true, files will be named using the pattern ${fileHash}-${basename}. For example, 34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico.
Resolves #4741
Updated dependencies [ 0c0949d]:
- miniflare@3.20240223.0

Wrangler Changelog

​​ 2024-03-14

​​ 3.34.2

​​ 3.34.1

​​ 3.34.0

​​ 2024-03-12

​​ 3.33.0

​​ 2024-03-07

​​ 3.32.0

​​ 2024-03-05

​​ 3.31.0

​​ 2024-02-29

​​ 3.30.1

​​ 2024-02-27

​​ 3.30.0