Wrangler
Minor Changes
- #8367
7b6b0c2Thanks @jonesphillip! - Deprecated--idparameter in favor of--namefor both thewrangler r2 bucket lifecycleandwrangler r2 bucket lockcommands
Minor Changes
Patch Changes
#8338
2d40989Thanks @GregBrimble! - feat: Upload _headers and _redirects if present with Workers Assets as part ofwrangler deployandwrangler versions upload.#8288
cf14e17Thanks @CarmenPopoviciu! - feat: Add assets Proxy Worker skeleton in miniflareThis commit implements a very basic Proxy Worker skeleton, and wires it in the "pipeline" miniflare creates for assets. This Worker will be incrementally worked on, but for now, the current implementation will forward all incoming requests to the Router Worker, thus leaving the current assets behaviour in local dev, the same.
This is an experimental feature available under the
--x-assets-rpcflag:wrangler dev --x-assets-rpc.#8216
af9a57aThanks @ns476! - Support Images binding inwrangler types#8304
fbba583Thanks @jahands! - chore: add concurrency and caching for Zone IDs and Workers routes lookupsWorkers with many routes can result in duplicate Zone lookups during deployments, making deployments unnecessarily slow. This compounded by the lack of concurrency when making these API requests.
This change deduplicates these requests and adds concurrency to help speed up deployments.
Minor Changes
#8256
f59d95bThanks @jbwcloudflare! - Add two new Queues commands: pause-delivery and resume-deliveryThese new commands allow users to pause and resume the delivery of messages to Queue Consumers
Patch Changes
#8274
fce642dThanks @emily-shen! - fix bindings to entrypoints on the same worker in workers with assets#8201
2cad136Thanks @ichernetsky-cf! - fix: interactively list Cloudchamber deployments using labels#8289
a4909cbThanks @penalosa! - Add the experimental--x-assets-rpcflag to gate feature work to support JSRPC with Workers + Assets projects.
Minor Changes
Patch Changes
Minor Changes
- #8253
6dd1e23Thanks @CarmenPopoviciu! - Add--cwdglobal argument to thewranglerCLI to allow changing the current working directory before running any command.
Patch Changes
Patch Changes
- #8175
eb46f98Thanks @edmundhung! - fix:unstable_splitSqlQueryshould ignore comments when splitting sql into statements
Patch Changes
#7687
cc853cfThanks @emily-shen! - fix: bug where Pages deployments that create new projects were failing with a new repo#8131
efd7f97Thanks @lambrospetrou! - D1 export will now show an error when the presigned URL is invalidUpdated dependencies [
5e06177]:
Patch Changes
- #8021
28b1dc7Thanks @0xD34DC0DE! - fix: prevent __cf_cjs name collision in the hybrid Nodejs compat plugin
Minor Changes
#8120
3fb801fThanks @sdnts! - Add a newupdatesubcommand for Queues to allow updating Queue settings#8120
3fb801fThanks @sdnts! - Allow overriding message retention duration when creating Queues#8026
542c6eaThanks @penalosa! - Add--outfiletowrangler deployfor generating a worker bundle.This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API
#8026
542c6eaThanks @penalosa! - Add awrangler check startupcommand to generate a CPU profile of your Worker's startup phase.This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.
Advanced usage:
--args: to customise the waywrangler check startupbuilds your Worker for analysis, provide the exact arguments you use when deploying your Worker withwrangler deploy. For instance, if you deploy your Worker withwrangler deploy --no-bundle, you should usewrangler check startup --args="--no-bundle"to profile the startup phase.--worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/
Patch Changes
#8112
fff677eThanks @penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata#8120
3fb801fThanks @sdnts! - Check bounds when overriding delivery delay when creating Queues#7950
4db1fb5Thanks @cmackenzie1! - Add local binding support for Worker Pipelines#8119
1bc60d7Thanks @penalosa! - Output correct config format fromwrangler d1 create. Previously, this command would always output TOML, regardless of the config file format#8130
1aa2a91Thanks @emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetryUser provided strings are still left redacted as always.
#8061
35710e5Thanks @emily-shen! - fix: respectWRANGLER_LOGinwrangler devPreviously,
--log-level=debugwas the only way to see debug logs inwrangler dev, which was unlike all other commands.Updated dependencies [
4db1fb5]:
Patch Changes
#8103
a025ad2Thanks @emily-shen! - fix: fix bug wherewrangler secret list --format=jsonwas printing the wrangler banner.Updated dependencies []:
Minor Changes
#7990
b1966dfThanks @cmsparks! - Add WRANGLER_CI_OVERRIDE_NAME for Workers CI#8028
b2dca9aThanks @emily-shen! - feat: Also log when no bindings are found.We currently print a worker's bindings during dev, versions upload and deploy. This just also prints something when there's no bindings found, in case you were expecting bindings.
#8037
71fd250Thanks @WillTaylorDev! - Provides unsafe.metadata configurations when using wrangler versions secret put.
Patch Changes
#8058
1f80d69Thanks @WillTaylorDev! - Bugfix: Modified versions secret put to inherit all known bindings, which circumvents a limitation in the API which does not return all fields for all bindings.#7986
88514c8Thanks @andyjessop! - docs: clarifies that local resources are "simulated locally" or "connected to remote resource", and adds console messages to help explain local dev#8008
9d08af8Thanks @ns476! - Add support for Images bindings (in private beta for now), with optional local support for platforms where Sharp is available.#7769
6abe69cThanks @cmackenzie1! - Adds the following new option forwrangler pipelines createandwrangler pipelines updatecommands:--cors-origins CORS origin allowlist for HTTP endpoint (use * for any origin) [array]#7290
0c0374cThanks @emily-shen! - fix: add support for workers with assets when running multiple workers in onewrangler devinstancehttps://github.com/cloudflare/workers-sdk/pull/7251 added support for running multiple Workers in one
wrangler dev/miniflare session. e.g.wrangler dev -c wrangler.toml -c ../worker2/wrangler.toml, which among other things, allowed cross-service RPC to Durable Objects.However this did not work in the same way as production when there was a Worker with assets - this PR should fix that.
#7769
6abe69cThanks @cmackenzie1! - Rename wrangler pipelines <create|update> flagsThe following parameters have been renamed:
Previous Name New Name access-key-id r2-access-key-id secret-access-key r2-secret-access-key transform transform-worker r2 r2-bucket prefix r2-prefix binding enable-worker-binding http enable-http authentication require-http-auth filename file-template filepath partition-template #8012
c412a31Thanks @mtlemilio! - Use fetchPagedListResult when listing Hyperdrive configs from the APIThis fixes an issue where only 20 configs were being listed.
#8077
60310cdThanks @emily-shen! - feat: add telemetry to experimental auto-provisioning
Patch Changes
#7988
444a630Thanks @edmundhung! - Fix #7985.This reverts the changes on #7945 that caused compatibility issues with Node 16 due to the introduction of
sharp.
Patch Changes
#7981
e2b3306Thanks @WalshyDev! - Fixes a regression introduced in Wrangler 3.107.0 in which[assets]was not being inherited from the top-level environment.Updated dependencies [
ab49886]:
Minor Changes
- #7897
34f9797Thanks @WillTaylorDev! - chore: providesrun_worker_firstfor Worker-script-first configuration. Deprecatesexperimental_serve_directly.
Patch Changes
#7945
d758215Thanks @ns476! - Add Images binding (in private beta for the time being)#7947
f57bc4eThanks @dario-piotrowicz! - fix: avoidgetPlatformProxylogging twice that it is using vars defined in.dev.varsfileswhen
getPlatformProxyis called and it retrieves values from.dev.varsfiles, it logs twice a message like:Using vars defined in .dev.vars, the changes here make sure that in such cases this log only appears once#7889
38db4edThanks @emily-shen! - feat: add experimental resource auto-provisioning to versions upload#7864
de6fa18Thanks @dario-piotrowicz! - Update theunstable_getMiniflareWorkerOptionstypes to always include anenvparameter.The
unstable_getMiniflareWorkerOptionstypes, when accepting a config object as the first argument, didn't accept a secondenvargument. The changes here make sure they do, since theenvis still relevant for picking up variables from.dev.varsfiles.#7964
bc4d6c8Thanks @LuisDuarte1! - Fix scripts binding to a workflow in a different script overriding workflow configUpdated dependencies [
cf4f47a]:
Minor Changes
#7856
2b6f149Thanks @emily-shen! - feat: add sanitised error messages to Wrangler telemetryError messages that have been audited for potential inclusion of personal information, and explicitly opted-in, are now included in Wrangler's telemetry collection. Collected error messages will not include any filepaths, user input or any other potentially private content.
#7900
bd9228eThanks @vicb! - chore(wrangler): update unenv dependency versionunenv@2.0.0-rc.1allows using the workerd implementation for the Node modulesnet,timers, andtimers/promises. Seeunjs/unenv#396.
Patch Changes
#7904
50b13f6Thanks @WalshyDev! - fix: validation for R2 bucket names, the regex was wrongly rejecting buckets starting with a number and the message wasn't as clear as it could be on what was going wrong.#7895
134d61dThanks @jahands! - Fix regression in retryOnAPIFailure preventing any requests from being retriedAlso fixes a regression in pipelines that prevented 401 errors from being retried when waiting for an API token to become active.
#7879
5c02e46Thanks @andyjessop! - Fix to not require local connection string when using Hyperdrive and wrangler dev --remote#7860
13ab591Thanks @vicb! - refactor(wrangler): make JSON parsing independent of NodeSwitch
jsonc-parserto parse json:JSON.parse()exception messages are not stable across Node versions- While
jsonc-parseris used, JSONC specific syntax is disabled
Updated dependencies []: