Bump the npm-dependencies group with 5 updates

[dependabot]

Bumps the npm-dependencies group with 5 updates:

Package	From	To
@graphql-tools/merge	9.1.2	9.1.6
@graphql-tools/schema	10.0.26	10.0.30
graphql-yoga	5.16.0	5.17.0
prettier	3.6.2	3.7.3
wrangler	4.45.3	4.51.0

Updates @graphql-tools/merge from 9.1.2 to 9.1.6

Changelog

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

9.1.6

Patch Changes

• Updated dependencies [2118a80]:
  • @​graphql-tools/utils@​10.11.0

9.1.5

Patch Changes

• Updated dependencies [2fe123a]:
  • @​graphql-tools/utils@​10.10.3

9.1.4

Patch Changes

• Updated dependencies [dddc5f6]:
  • @​graphql-tools/utils@​10.10.2

9.1.3

Patch Changes

• Updated dependencies [fbb58b5]:
  • @​graphql-tools/utils@​10.10.1

Commits

• 7b17d1f chore(release): update monorepo packages versions (#7722)
• 8e2f481 chore(release): update monorepo packages versions (#7684)
• 53fdba6 chore(release): update monorepo packages versions (#7680)
• 7f1859f build(deps): bump the actions-deps group with 5 updates (#7667)
• 5b26b6d chore(release): update monorepo packages versions (#7655)
• See full diff in compare view

Updates @graphql-tools/schema from 10.0.26 to 10.0.30

Changelog

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

10.0.30

Patch Changes

• Updated dependencies [2118a80]:
  • @​graphql-tools/utils@​10.11.0
  • @​graphql-tools/merge@​9.1.6

10.0.29

Patch Changes

• Updated dependencies [2fe123a]:
  • @​graphql-tools/utils@​10.10.3
  • @​graphql-tools/merge@​9.1.5

10.0.28

Patch Changes

• Updated dependencies [dddc5f6]:
  • @​graphql-tools/utils@​10.10.2
  • @​graphql-tools/merge@​9.1.4

10.0.27

Patch Changes

• Updated dependencies [fbb58b5]:
  • @​graphql-tools/utils@​10.10.1
  • @​graphql-tools/merge@​9.1.3

Commits

• 7b17d1f chore(release): update monorepo packages versions (#7722)
• 8e2f481 chore(release): update monorepo packages versions (#7684)
• 53fdba6 chore(release): update monorepo packages versions (#7680)
• 5b26b6d chore(release): update monorepo packages versions (#7655)
• See full diff in compare view

Updates graphql-yoga from 5.16.0 to 5.17.0

Changelog

Sourced from graphql-yoga's changelog.

5.17.0

Minor Changes

• #4288 66c370c Thanks @​EmrysMyrddin! - Add experimental support for coordinate error attribute proposal.

  The coordinate attribute indicates the coordinate in the schema of the resolver which experienced the errors. It allows for an easier error source identification than with the path which can be difficult to walk, or even lead to unsolvable ambiguities when using Union or Interface types.

  Usage

  Since this is experimental, it has to be explicitly enabled by adding the appropriate plugin to the Yoga instance:

  import { createYoga, useErrorCoordinate } from 'graphql-yoga'
  import { schema } from './schema'
  export const yoga = createYoga({
  schema,
  plugins: [useErrorCoordinate()]
  })

  Once enabled, located errors will gain the coordinate attribute:

  const myPlugin = {
    onExecutionResult({ result }) {
      if (result.errors) {
        for (const error of result.errors) {
          console.log('Error at', error.coordinate, ':', error.message)
        }
      }
    }
  }

  Security concerns

  Adding a schema coordinate to errors exposes information about the schema, which can be an attack vector if you rely on the fact your schema is private and secret.

  This is why the coordinate attribute is not serialized by default, and will not be exposed to clients.

... (truncated)

Commits

• e1079f6 chore(release): update monorepo packages versions (#4300)
• 66c370c feat(graphql-yoga): add support for experimental error coordinate (#4288)
• 0517886 chore(deps): update dependency globby to v16 (#4289)
• 8d7e5f0 chore(release): update monorepo packages versions (#4268)
• b8d2f70 fix(deps): update envelop (major) (#4278)
• ba38629 fix: handleError sets unexpected flag correctly in the error extensions (...
• 654365a chore(release): update monorepo packages versions (#4204)
• e1f52b6 chore(deps): update typescript-eslint monorepo to v8.46.3 (#4264)
• 6f83cea fix(server): bump whatwg-node to fix Bun.serve compatibility (#4263)
• 9a40ab0 fix(deps): update nextjs monorepo to v16 (major) (#4239)
• Additional commits viewable in compare view

Updates prettier from 3.6.2 to 3.7.3

Release notes

Sourced from prettier's releases.

3.7.3

What's Changed

• Fix prettier.getFileInfo() change that breaks VSCode extension by @​fisker in prettier/prettier#18375

🔗 Changelog

3.7.2

What's Changed

• Fix string print when switching quotes by @​fisker in prettier/prettier#18351
• Preserve quote for embedded HTML attribute values by @​kovsu in prettier/prettier#18352
• Fix comment in empty type literal by @​fisker in prettier/prettier#18364

🔗 Changelog

3.7.1

• Fix performance regression in doc printer (#18342 by @​fisker)

🔗 Changelog

3.7.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.7.3

diff

API: Fix prettier.getFileInfo() change that breaks VSCode extension (#18375 by @​fisker)

An internal refactor accidentally broke the VSCode extension plugin loading.

3.7.2

diff

JavaScript: Fix string print when switching quotes (#18351 by @​fisker)

// Input
console.log("A descriptor\\'s .kind must be \"method\" or \"field\".")
// Prettier 3.7.1
console.log('A descriptor\'s .kind must be "method" or "field".');
// Prettier 3.7.2
console.log('A descriptor\'s .kind must be "method" or "field".');

JavaScript: Preserve quote for embedded HTML attribute values (#18352 by @​kovsu)

// Input
const html = /* HTML */ ` <div class="${styles.banner}"></div> `;
// Prettier 3.7.1
const html = /* HTML */ &lt;div class=${styles.banner}&gt;&lt;/div&gt;;
// Prettier 3.7.2
const html = /* HTML */ &lt;div class=&quot;${styles.banner}&quot;&gt;&lt;/div&gt;;

TypeScript: Fix comment in empty type literal (#18364 by @​fisker)

// Input
export type XXX = {
  // tbd
};
// Prettier 3.7.1
</tr></table>

... (truncated)

Commits

• fdfa670 Release 3.7.3
• 2dce3ec Fix typo
• 27d6c64 Revert previous change to getFileInfo (#18375)
• f4a7afa Add types for config related functions (#18376)
• 9266e3e Add resolved test cases (#18358)
• 3bfc014 Bump Prettier dependency to 3.7.2
• 081b846 Clean changelog_unreleased
• 03384c9 Release 3.7.2
• 514e51a Release @​prettier/plugin-hermes & @​prettier/plugin-oxc v0.1.2
• 29a11ae Fix comment in empty type literal (#18364)
• 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 prettier since your current version.

Updates wrangler from 4.45.3 to 4.51.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #11345 d524e55 Thanks @​penalosa! - Enable experimental support for autoconfig-powered Astro projects

• #11228 43903a3 Thanks @​petebacondarwin! - Support CLOUDFLARE_ENV environment variable for selecting the active environment

  This change enables users to select the environment for commands such as CLOUDFLARE_ENV=prod wrangler versions upload. The --env command line argument takes precedence.

  The CLOUDFLARE_ENV environment variable is mostly used with the @cloudflare/vite-plugin to select the environment for building the Worker to be deployed. This build also generates a "redirected deploy config" that is flattened to only contain the active environment. To avoid accidentally deploying a version that is built for one environment to a different environment, there is an additional check to ensure that if the user specifies an environment in Wrangler it matches the original selected environment from the build.

Patch Changes

• #11367 e496280 Thanks @​vicb! - Rate limit r2 bulk put

• Updated dependencies [4d61fae, 69f4dc3, 1133c4d, 4d61fae]:

  • @​cloudflare/kv-asset-handler@​0.4.1
  • [email protected]

[email protected]

Minor Changes

• #11219 524a6e5 Thanks @​Ltadrian! - Implement Hyperdrive binding TLS miniflare proxy. This will allow for wrangler dev hyperdrive bindings to connect to external databases that require TLS.

• #11233 c922a81 Thanks @​emily-shen! - Add containers.unsafe to allow internal users to use additional container features

Patch Changes

• #11353 0cf696d Thanks @​vicb! - Use the native node:domain module when available

  It is enabled when the enable_nodejs_domain_module compatibility flag is set.

• #11328 bb44120 Thanks @​ascorbic! - Fixes a bug that caused wrangler deploy to hang when deploying SvelteKit sites with experimental autoconfig

• #11025 4a158e9 Thanks @​devin-ai-integration! - Use the native node:wasi module when available

  It is enabled when the enable_nodejs_wasi_module compatibility flag is set.

• Updated dependencies [0cf696d, 524a6e5, 4a158e9]:

  • @​cloudflare/unenv-preset@​2.7.11
  • [email protected]

[email protected]

Patch Changes

• #11344 c758809 Thanks @​dario-piotrowicz! - Fix: mark the r2 bulk command as hidden and experimental

• #11339 dfba912 Thanks @​dario-piotrowicz! - Fix wrangler deploy erroring when it pulls down remote configs of workers containing an assets binding

... (truncated)

Commits

• f87b057 Version Packages (#11374)
• 1133c4d chore(deps): bump the workerd-and-workers-types group with 2 updates (#11396)
• 43903a3 Support CLOUDFLARE_ENV environment variable for selecting the active enviro...
• 235142e Improve stability of wrangler dev related tests (#11182)
• 9365b02 test: make the startWorker e2e test more resilient to flakes (#11347)
• aa4a5f1 Move findWranglerConfig tests to workers-utils (#11349)
• 4d61fae modernize kv-asset-handler so that we can test is in Node 22+ (#11348)
• 69f4dc3 chore(deps): bump the workerd-and-workers-types group with 2 updates (#11376)
• e496280 Rate limit r2 bulk put (#11367)
• 86eab8e Version Packages (#11356)
• 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 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>.