Wrangler
Patch Changes
#7141
d938bb3
Thanks @emily-shen! - fix: throw a better error if there is an "ASSETS" user binding in a Pages projects#7124
f8ebdd1
Thanks @skepticfx! - fix: Modify Cloudchamber deployment labels in interactive mode
Minor Changes
#6999
0111edb
Thanks @garvit-gupta! - docs: Vectorize GA Announcement Banner#6916
a33a133
Thanks @garrettgu10! - Local development now supports Vectorize bindings#7004
15ef013
Thanks @garvit-gupta! - feat: Enable Vectorize query by id via Wrangler#7092
038fdd9
Thanks @jonesphillip! - Added location hint option for the Wrangler R2 bucket create command#7024
bd66d51
Thanks @xortive! - feature: allow using a connection string when updating hyperdrive configsboth
hyperdrive create
andhyperdrive update
now support updating configs with connection strings.
Patch Changes
#7091
68a2a84
Thanks @taylorlee! - fix: synchronize observability settings duringwrangler versions deploy
When running
wrangler versions deploy
, Wrangler will now updateobservability
settings in addition tologpush
andtail_consumers
. Unlikewrangler deploy
, it will not disable observability whenobservability
is undefined inwrangler.toml
.#7080
924ec18
Thanks @vicb! - chore(wrangler): update unenv dependency version#7097
8ca4b32
Thanks @emily-shen! - fix: remove deprecation warnings forwrangler init
We will not be removing
wrangler init
(it just delegates to create-cloudflare now). These warnings were causing confusion for users as itwrangler init
is still recommended in many places.#7073
656a444
Thanks @penalosa! - Internal refactor to removees-module-lexer
and supportwrangler types
for Workers with Durable Objects & JSX#7024
bd66d51
Thanks @xortive! - fix: make individual parameters work forwrangler hyperdrive create
when not using HoAwrangler hyperdrive create
individual parameters were not setting the database name correctly when calling the api.#7024
bd66d51
Thanks @xortive! - refactor: use same param parsing code forwrangler hyperdrive create
andwrangler hyperdrive update
ensures that going forward, both commands support the same features and have the same names for config flags
Minor Changes
- #7000
1de309b
Thanks @jkoe-cf! - feature: allowing users to specify a description when creating an event notification rule
Patch Changes
#7011
cef32c8
Thanks @GregBrimble! - fix: Correctly apply Durable Object migrations for namespaced scripts#7067
4aa35c5
Thanks @LuisDuarte1! - Change trigger command to comply with the current workflows endpoint.This also adds an id option to allow users to optionally customize the new instance id.
#7082
3f1d79c
Thanks @LuisDuarte1! - Change to new terminate instance workflow endpoint#7036
e7ea600
Thanks @penalosa! - Reduce KV bulk upload bucket size to 1000 (from the previous 5000)#7068
a2afcf1
Thanks @RamIdeas! - log warning of Workflows open-beta status when running deploying a Worker that contains a Workflow binding#7065
b219296
Thanks @penalosa! - Internal refactor to remove React/ink from all non-wrangler dev
flows#7064
a90980c
Thanks @penalosa! - Fixwrangler dev --remote --show-interactive-dev-session=false
by only enabling hotkeys after account selection if hotkeys were previously enabled#7045
5ef6231
Thanks @RamIdeas! - Add preliminary support for Workflows in wrangler dev#7075
80e5bc6
Thanks @LuisDuarte1! - Fix params serialization when send the trigger workflow APIPreviously, wrangler did not parse the params sending it as a string to workflow's services.
Updated dependencies [
760e43f
,8dc2b7d
,5ef6231
]:- miniflare@3.20241022.0
- @cloudflare/workers-shared@0.7.0
Minor Changes
- #6945
6b97353
Thanks @bthwaites! - Add jurisdiction option to R2 event notification wrangler actions
Patch Changes
#5737
9bf51d6
Thanks @penalosa! - Validate duplicate bindings across all binding types#7010
1f6ff8b
Thanks @vicb! - chore: update unenv dependency version#7012
244aa57
Thanks @RamIdeas! - Add support for Workflow bindings (in deployments, not yet in local dev)To bind to a workflow, add a
workflows
section in your wrangler.toml:[[workflows]] binding = "WORKFLOW" name = "my-workflow" class_name = "MyDemoWorkflow"
and export an entrypoint (e.g.
MyDemoWorkflow
) in your script:import { WorkflowEntrypoint } from "cloudflare:workers"; export class MyDemoWorkflow extends WorkflowEntrypoint<Env, Params> {...}
#7039
e44f496
Thanks @penalosa! - Only show dev registry connection status in local dev#7037
e1b93dc
Thanks @emily-shen! - fix: ask for confirmation before creating a new Worker when uploading secretsPreviously,
wrangler secret put KEY --name non-existent-worker
would automatically create a new Worker with the namenon-existent-worker
. This fix asks for confirmation before doing so (if running in an interactive context). Behaviour in non-interactive/CI contexts should be unchanged.#7015
48152d6
Thanks @RamIdeas! - addwrangler workflows ...
commands#7041
045787b
Thanks @CarmenPopoviciu! - Showwrangler pages dev --proxy
warningOn Node.js 17+, wrangler will default to fetching only the IPv6 address. With these changes we warn users that the process listening on the port specified via
--proxy
should be configured for IPv6.#7018
127615a
Thanks @emily-shen! - fix: log successful runs ofd1 execute
in local#6970
a8ca700
Thanks @oliy! - Add HTTP authentication options for Workers Pipelines#7005
6131ef5
Thanks @edmundhung! - fix: prevent users from passing multiple arguments to non array options#7046
f9d5fdb
Thanks @oliy! - Minor change to 3rd party API shape for Workers Pipelines#6972
c794935
Thanks @penalosa! - Add(local)
indicator to bindings using local dataUpdated dependencies [
809193e
]:
Minor Changes
- #6990
586c253
Thanks @courtney-sims! - feat: Adds new detailed pages deployment output type
Patch Changes
#6963
a5ac45d
Thanks @RamIdeas! - fix: makewrangler dev --remote
respect wrangler.toml'saccount_id
property.This was a regression in the
--x-dev-env
flow recently turned on by default.#6996
b8ab809
Thanks @emily-shen! - fix: improve error messaging when accidentally using Workers commands in Pages projectIf we detect a Workers command used with a Pages project (i.e. wrangler.toml contains
pages_output_build_dir
), error with Pages version of command rather than "missing entry-point" etc.