Bump the npm-dependencies group with 3 updates

[dependabot]

Bumps the npm-dependencies group with 3 updates: @graphql-tools/merge, @graphql-tools/schema and wrangler.

Updates @graphql-tools/merge from 9.1.1 to 9.1.2

Changelog

Sourced from @​graphql-tools/merge's changelog.

9.1.2

Patch Changes

• Updated dependencies [fd105f4, fded91e, 3b99a9b]:
  • @​graphql-tools/utils@​10.10.0

Commits

• 823336c chore(release): update monorepo packages versions (#7514)
• 6e75e35 build(deps): bump the actions-deps group across 1 directory with 3 updates (#...
• 1a6251d fix: link merging (#6964)
• 42419d2 Bump the actions-deps group with 4 updates (#7511)
• 5c36e43 Bump the actions-deps group across 1 directory with 9 updates (#7503)
• 684fd10 fix(deps): update graphql-tools (major) (#7449)
• 7563177 chore(release): update monorepo packages versions (#7300)
• 0f8a76c Replace dependency @​theguild/federation-composition in graphqlt-tools/merge (...
• 21014b3 chore(release): update monorepo packages versions (#7241)
• 5936d8d fix(deps): update dependency @​theguild/federation-composition to ^0.19.0 (#7276)
• Additional commits viewable in compare view

Updates @graphql-tools/schema from 10.0.25 to 10.0.26

Changelog

Sourced from @​graphql-tools/schema's changelog.

10.0.26

Patch Changes

• Updated dependencies [fd105f4, fded91e, 3b99a9b]:
  • @​graphql-tools/utils@​10.10.0
  • @​graphql-tools/merge@​9.1.2

Commits

• 823336c chore(release): update monorepo packages versions (#7514)
• 129699b chore(deps): update dependency graphql-scalars to v1.25.0 (#7592)
• 1745485 fix(deps): update all non-major dependencies (#7431)
• 7563177 chore(release): update monorepo packages versions (#7300)
• 21014b3 chore(release): update monorepo packages versions (#7241)
• b95aa53 chore(deps): update dependency graphql-scalars to v1.24.2 (#7046)
• 2e14338 chore(release): update monorepo packages versions (#7030)
• 45ff11b chore(release): update monorepo packages versions (#7024)
• af06ffd chore(release): update monorepo packages versions (#6993)
• 0e08114 chore(release): update monorepo packages versions (#6973)
• Additional commits viewable in compare view

Updates wrangler from 4.40.3 to 4.45.3

Release notes

Sourced from wrangler's releases.

[email protected]

Patch Changes

• #11117 6822aaf Thanks @​emily-shen! - fix: show local/remote status before D1 command confirmations

  D1 commands (execute, export, migrations apply, migrations list, delete, time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.

• #11077 bce8142 Thanks @​petebacondarwin! - Ensure that process.env is case-insensitive on Windows

  The object that holds the environment variables in process.env does not care about the case of its keys in Windows. For example, process.env.SystemRoot and process.env.SYSTEMROOT will refer to the same value.

  Previously, when merging fields from .env files we were replacing this native object with a vanilla JavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing when in reality they just had different casing.

[email protected]

Patch Changes

• #10959 d0208fe Thanks @​devin-ai-integration! - Fixed conflict between --env and --expires flags in wrangler r2 object put.

  --e now aliases --env only, and NOT --expires.

• #10915 dbe51c1 Thanks @​devin-ai-integration! - Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself.

• #10913 d4f2daf Thanks @​devin-ai-integration! - Fixed duplicate warning messages appearing during wrangler dev when configuration changes or state transitions occur

[email protected]

Minor Changes

• #11030 1a8088a Thanks @​penalosa! - Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the --no-x-provision flag. It currently works for R2, D1, and KV bindings.

  To use this feature, add a binding to your config file without a resource ID:

  {
  	"kv_namespaces": [{ "binding": "MY_KV" }],
  	"d1_databases": [{ "binding": "MY_DB" }],
  	"r2_buckets": [{ "binding": "MY_R2" }],
  }

  wrangler dev will automatically create these resources for you locally, and when you next run wrangler deploy Wrangler will call the Cloudflare API to create the requested resources and link them to your Worker. They'll stay linked across deploys, and you don't need to add the resource IDs to the config file for future deploys to work. This is especially good for shared templates, which now no longer need to include account-specific resource ID when adding a binding.

Patch Changes

• #11037 4bd4c29 Thanks @​danielrs! - Better Wrangler subdomain defaults warning.

  Improves the warnings that we show users when either worker_dev or preview_urls are missing.

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.45.3

Patch Changes

• #11117 6822aaf Thanks @​emily-shen! - fix: show local/remote status before D1 command confirmations

  D1 commands (execute, export, migrations apply, migrations list, delete, time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.

• #11077 bce8142 Thanks @​petebacondarwin! - Ensure that process.env is case-insensitive on Windows

  The object that holds the environment variables in process.env does not care about the case of its keys in Windows. For example, process.env.SystemRoot and process.env.SYSTEMROOT will refer to the same value.

  Previously, when merging fields from .env files we were replacing this native object with a vanilla JavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing when in reality they just had different casing.

4.45.2

Patch Changes

• #11097 55657eb Thanks @​penalosa! - Extract internal APIs into a new @cloudflare/workers-utils package

• #11118 d47f166 Thanks @​zebp! - Fix validation of the persist field of observability logs and traces configuration

4.45.1

Patch Changes

• #10959 d0208fe Thanks @​devin-ai-integration! - Fixed conflict between --env and --expires flags in wrangler r2 object put.

  --e now aliases --env only, and NOT --expires.

• #10915 dbe51c1 Thanks @​devin-ai-integration! - Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself.

• #10913 d4f2daf Thanks @​devin-ai-integration! - Fixed duplicate warning messages appearing during wrangler dev when configuration changes or state transitions occur

4.45.0

Minor Changes

• #11030 1a8088a Thanks @​penalosa! - Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the --no-x-provision flag. It currently works for R2, D1, and KV bindings.

  To use this feature, add a binding to your config file without a resource ID:

  {
  	"kv_namespaces": [{ "binding": "MY_KV" }],
  	"d1_databases": [{ "binding": "MY_DB" }],
  	"r2_buckets": [{ "binding": "MY_R2" }],

... (truncated)

Commits

• 8445f29 Version Packages (#11131)
• 6822aaf print d1 resource locations take 2 (#11117)
• bce8142 Ensure that process.env is case-insensitive on Windows (#11077)
• 6958fa7 Version Packages (#11115)
• d47f166 Fix validation of the persist field of observability logs and traces (#11118)
• 55657eb Extract a publishable @cloudflare/workers-utils package (#11097)
• fbbb1da Revert "fix: add printResourceLocation to D1 commands (#10912)" (#11116)
• 1357ca2 fix: add printResourceLocation to D1 commands (#10912)
• cb47614 Version Packages (#11085)
• d0208fe [wrangler] Fix --env and --expires flag conflict in r2 object put (#10959)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for wrangler since your current version.

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will 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 version will 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

[github-actions]

👋 Thanks for opening a pull request!

If you are new, please check out the trimmed down summary of our deployment process below:

1. 👀 Observe the CI jobs and tests to ensure they are passing

2. ✔️ Obtain an approval/review on this pull request

3. 🚀 Deploy your pull request to the development environment with .deploy to development

4. 🚀 Deploy your pull request to the production environment with .deploy

   If anything goes wrong, rollback with .deploy main

5. 🎉 Merge!

Need help? Type .help as a comment or visit the usage guide for more details

Please note, if you have a more complex change, it is advised to claim a deployment lock with .lock <environment> --reason <reason> to prevent other deployments from happening while you are working on your change.

Once your PR has been merged, you can remove the lock with .unlock <environment>.