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 contains the following updates:
4.20241011.0
->4.20241022.0
3.80.5
->3.82.0
Release Notes
cloudflare/workerd (@cloudflare/workers-types)
v4.20241022.0
Compare Source
v4.20241018.0
Compare Source
cloudflare/workers-sdk (wrangler)
v3.82.0
Compare Source
Minor Changes
6b97353
Thanks @bthwaites! - Add jurisdiction option to R2 event notification wrangler actionsPatch 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:and export an entrypoint (e.g.
MyDemoWorkflow
) in your script:#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
]:v3.81.0
Compare Source
Minor Changes
586c253
Thanks @courtney-sims! - feat: Adds new detailed pages deployment output typePatch 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.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.