chore(deps-dev): bump the dev-deps group across 1 directory with 2 updates
Bumps the dev-deps group with 2 updates in the / directory: typescript and wrangler.
Updates typescript from 5.6.2 to 5.6.3
Release notes
Sourced from typescript's releases.
TypeScript 5.6.3
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
- fixed issues query for Typescript 5.6.0 (Beta).
- fixed issues query for Typescript 5.6.1 (RC).
- fixed issues query for Typescript 5.6.2 (Stable).
- fixed issues query for Typescript 5.6.3 (Stable).
Downloads are available on:
Commits
d48a5cfBump version to 5.6.3 and LKGfefa70a🤖 Pick PR #60083 (Don't issue implicit any when obtai...) into release-5.6 (#...ff71692[release-5.6] Remove tsbuildInfo specification error now that we need it for ...1f44dcf🤖 Pick PR #60157 (fix automatic type acquisition) into release-5.6 (#60169)- See full diff in compare view
Updates wrangler from 3.78.7 to 3.82.0
Release notes
Sourced from wrangler's releases.
[email protected]
Minor Changes
- #6945
6b97353Thanks@​bthwaites! - Add jurisdiction option to R2 event notification wrangler actionsPatch Changes
#5737
9bf51d6Thanks@​penalosa! - Validate duplicate bindings across all binding types#7010
1f6ff8bThanks@​vicb! - chore: update unenv dependency version#7012
244aa57Thanks@​RamIdeas! - Add support for Workflow bindings (in deployments, not yet in local dev)To bind to a workflow, add a
workflowssection 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
e44f496Thanks@​penalosa! - Only show dev registry connection status in local dev#7037
e1b93dcThanks@​emily-shen! - fix: ask for confirmation before creating a new Worker when uploading secretsPreviously,
wrangler secret put KEY --name non-existent-workerwould 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
48152d6Thanks@​RamIdeas! - addwrangler workflows ...commands#7041
045787bThanks@​CarmenPopoviciu! - Showwrangler pages dev --proxywarningOn 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
--proxyshould be configured for IPv6.#7018
127615aThanks@​emily-shen! - fix: log successful runs ofd1 executein local#6970
a8ca700Thanks@​oliy! - Add HTTP authentication options for Workers Pipelines#7005
6131ef5Thanks@​edmundhung! - fix: prevent users from passing multiple arguments to non array options#7046
f9d5fdbThanks@​oliy! - Minor change to 3rd party API shape for Workers Pipelines
... (truncated)
Changelog
Sourced from wrangler's changelog.
3.82.0
Minor Changes
- #6945
6b97353Thanks@​bthwaites! - Add jurisdiction option to R2 event notification wrangler actionsPatch Changes
#5737
9bf51d6Thanks@​penalosa! - Validate duplicate bindings across all binding types#7010
1f6ff8bThanks@​vicb! - chore: update unenv dependency version#7012
244aa57Thanks@​RamIdeas! - Add support for Workflow bindings (in deployments, not yet in local dev)To bind to a workflow, add a
workflowssection 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
e44f496Thanks@​penalosa! - Only show dev registry connection status in local dev#7037
e1b93dcThanks@​emily-shen! - fix: ask for confirmation before creating a new Worker when uploading secretsPreviously,
wrangler secret put KEY --name non-existent-workerwould 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
48152d6Thanks@​RamIdeas! - addwrangler workflows ...commands#7041
045787bThanks@​CarmenPopoviciu! - Showwrangler pages dev --proxywarningOn 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
--proxyshould be configured for IPv6.#7018
127615aThanks@​emily-shen! - fix: log successful runs ofd1 executein local#6970
a8ca700Thanks@​oliy! - Add HTTP authentication options for Workers Pipelines#7005
6131ef5Thanks@​edmundhung! - fix: prevent users from passing multiple arguments to non array options#7046
f9d5fdbThanks@​oliy! - Minor change to 3rd party API shape for Workers Pipelines
... (truncated)
Commits
8d03647Version Packages (#7019)9bf51d6Validate duplicate bindings across all binding types (#5737)e1b93dcfix: ask for confirmation before creating a new worker when uploading secrets...6131ef5fix(wrangler): enforce single value on non-array arguments (#7005)6b97353Add jurisdiction option to R2 event notification wrangler actions (#6945)127615afix: log successful execution of D1 commands locally (#7018)045787bfix(wrangler): Showwrangler pages dev --proxywarning (#7041)f9d5fdbPIPE-37 Small API restructuring for Worker Pipelines (#7046)a8ca700PIPE-37 Add authenticated HTTP source options to Worker Pipelines (#6970)e44f496Only show dev registry connection status in local dev (#7039)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions