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
[email protected]
Minor Changes
78c1649
Thanks @andyjessop! - chore: remove nodejs_compat flag from basic C3 templates[email protected]
Minor Changes
78bdec5
Thanks @penalosa! - Support theCF-Connecting-IP
header, which will be available in your Worker to determine the IP address of the client that initiated a request.Patch Changes
2c76887
Thanks @lambrospetrou! - Fix D1 exports to properly pad HEX strings for binary values.@cloudflare/[email protected]
Minor Changes
8b48ca6
Thanks @GregBrimble! - feat: Return a 304 Not Modified response when matching an asset preservation cache request if appropriatePatch Changes
#7561
8b48ca6
Thanks @GregBrimble! - chore: Remove now-unused asset preservation cache (v1)#7561
8b48ca6
Thanks @GregBrimble! - fix: Store an empty result when Early Hints parsing returns nothing or errors. Previously, we weren't storing anything which resulted in Early Hints being parsed on every request.Updated dependencies [
2c76887
,78bdec5
]:@cloudflare/[email protected]
Minor Changes
#7697
3e2bede
Thanks @vicb! - chore(unenv-preset): drop unused .cjs filesOnly .mjs files are used.
@cloudflare/[email protected]
Minor Changes
78c1649
Thanks @andyjessop! - chore: add nodejs_compat by default in Vitest Pool WorkersPatch Changes
ff4e77e
,2c76887
,6439347
,e771fe9
,7c8ae1c
,78bdec5
,45d1d1e
,e4716cc
,773bda8
,9d2740a
,f3c2f69
]:[email protected]
Minor Changes
#7534
7c8ae1c
Thanks @cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines#7674
45d1d1e
Thanks @Ankcorn! - Add support for env files to wrangler secret bulk i.e..dev.vars
Run
wrangler secret bulk .dev.vars
to add the env fileThis will upload the secrets KEY and KEY_2 to your worker
#7442
e4716cc
Thanks @petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commandsThis new feature is designed for build tools and frameworks to provide a deploy-specific configuration,
which Wrangler can use instead of user configuration when running deploy-related commands.
It is not expected that developers of Workers will need to use this feature directly.
Affected commands
The commands that use this feature are:
wrangler deploy
wrangler dev
wrangler versions upload
wrangler versions deploy
wrangler pages deploy
wrangler pages build
wrangler pages build-env
Config redirect file
When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path
.wrangler/deploy/config.json
. This file must contain only a single JSON object of the form:When this file exists Wrangler will follow the
configPath
(relative to the.wrangler/deploy/config.json
file) to find an alternative Wrangler configuration file to load and use as part of this command.When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.
Custom build tool example
A common approach that a build tool might choose to implement.
The user writes code that uses Cloudflare Workers resources, configured via a user
wrangler.toml
file.Note that this configuration points
main
at user code entry-point.The user runs a custom build, which might read the
wrangler.toml
to find the entry-point:> my-tool build
This tool generates a
dist
directory that contains both compiled code and a new deployment configuration file, but also a.wrangler/deploy/config.json
file that redirects Wrangler to this new deployment configuration file:The
dist/wrangler.json
will contain:And the
.wrangler/deploy/config.json
will contain:#7685
9d2740a
Thanks @vicb! - allow overriding the unenv preset.By default wrangler uses the bundled unenv preset.
Setting
WRANGLER_UNENV_RESOLVE_PATHS
allow to use another version of the preset.Those paths are used when resolving the unenv module identifiers to absolute paths.
This can be used to test a development version.
#7694
f3c2f69
Thanks @joshthoward! - Default wrangler d1 export to --local rather than failingPatch Changes
#7456
ff4e77e
Thanks @andyjessop! - chore: removes --experimental-versions flag, as versions is now GA.#7712
6439347
Thanks @penalosa! - Remove CF-Connecting-IP for requests to the edge preview#7703
e771fe9
Thanks @petebacondarwin! - include the top level Worker name in the parsed config structure#7576
773bda8
Thanks @cmackenzie1! - Remove defaults forbatch-max-*
pipeline parameters and define value rangesUpdated dependencies [
2c76887
,78bdec5
]:@cloudflare/[email protected]
Patch Changes
65a3e35
Thanks @emily-shen! - chore: rebases patches on latest devtools head