nestjs-cls icon indicating copy to clipboard operation
nestjs-cls copied to clipboard
verified publisher icon Papooch

build(deps-dev): bump the graphql group across 2 directories with 3 updates

Open dependabot[bot] opened this issue 5 months ago • 0 comments

Bumps the graphql group with 3 updates in the / directory: @apollo/server, graphql and mercurius. Bumps the graphql group with 1 update in the /packages/core directory: @apollo/server.

Updates @apollo/server from 4.12.2 to 5.2.0

Release notes

Sourced from @​apollo/server's releases.

@​apollo/server-integration-testsuite@​5.2.0

Patch Changes

  • Updated dependencies [51acbeb]:
    • @​apollo/server@​5.2.0

@​apollo/server@​5.2.0

Minor Changes

  • #8161 51acbeb Thanks @​jerelmiller! - Fix an issue where some bundlers would fail to build because of the dynamic import for the optional peer dependency on @yaacovcr/transform introduced in @apollo/server 5.1.0. To provide support for the legacy incremental format, you must now provide the legacyExperimentalExecuteIncrementally option to the ApolloServer constructor.

    import { legacyExecuteIncrementally } from '@yaacovcr/transform';

    const server = new ApolloServer({
// ...
legacyExperimentalExecuteIncrementally: legacyExecuteIncrementally,
});

    If the legacyExperimentalExecuteIncrementally option is not provided and the client sends an Accept header with a value of multipart/mixed; deferSpec=20220824, an error is returned by the server.

@​apollo/server-integration-testsuite@​5.1.0

Patch Changes

  • Updated dependencies [80a1a1a]:
    • @​apollo/server@​5.1.0

@​apollo/server@​5.1.0

Minor Changes

  • #8148 80a1a1a Thanks @​jerelmiller! - Apollo Server now supports the incremental delivery protocol (@defer and @stream) that ships with [email protected]. To use the current protocol, clients must send the Accept header with a value of multipart/mixed; incrementalSpec=v0.2.

    Upgrading to 5.1 will depend on what version of graphql you have installed and whether you already support the incremental delivery protocol.

    I use graphql@16 without incremental delivery

    Continue using graphql v16 with no additional changes. Incremental delivery won't be available.

    I use graphql@16 but would like to add support for incremental delivery

    Install [email protected] and follow the "Incremental delivery" guide to add the @defer and @stream directives to your schema. Clients should send the Accept header with a value of multipart/mixed; incrementalSpec=v0.2 to get multipart responses.

    I use [email protected] and use incremental delivery

    You must upgrade to [email protected] to continue using incremental delivery. If you'd like to continue providing support for the legacy incremental protocol, install the @yaacovcr/transform package. Apollo Server will attempt to load this module when the client specifies an Accept header with a value of multipart/mixed; deferSpec=20220824. If this package is not installed, an error is returned by the server.

    Because Apollo Server now supports multiple versions of the incremental delivery types, the existing incremental delivery types have been renamed with an Alpha2 suffix. If you import these types in your code, you will need to add the Alpha2 suffix.

... (truncated)

Changelog

Sourced from @​apollo/server's changelog.

5.2.0

Minor Changes

  • #8161 51acbeb Thanks @​jerelmiller! - Fix an issue where some bundlers would fail to build because of the dynamic import for the optional peer dependency on @yaacovcr/transform introduced in @apollo/server 5.1.0. To provide support for the legacy incremental format, you must now provide the legacyExperimentalExecuteIncrementally option to the ApolloServer constructor.

    import { legacyExecuteIncrementally } from '@yaacovcr/transform';

    const server = new ApolloServer({
// ...
legacyExperimentalExecuteIncrementally: legacyExecuteIncrementally,
});

    If the legacyExperimentalExecuteIncrementally option is not provided and the client sends an Accept header with a value of multipart/mixed; deferSpec=20220824, an error is returned by the server.

5.1.0

Minor Changes

  • #8148 80a1a1a Thanks @​jerelmiller! - Apollo Server now supports the incremental delivery protocol (@defer and @stream) that ships with [email protected]. To use the current protocol, clients must send the Accept header with a value of multipart/mixed; incrementalSpec=v0.2.

    Upgrading to 5.1 will depend on what version of graphql you have installed and whether you already support the incremental delivery protocol.

    I use graphql@16 without incremental delivery

    Continue using graphql v16 with no additional changes. Incremental delivery won't be available.

    I use graphql@16 but would like to add support for incremental delivery

    Install [email protected] and follow the "Incremental delivery" guide to add the @defer and @stream directives to your schema. Clients should send the Accept header with a value of multipart/mixed; incrementalSpec=v0.2 to get multipart responses.

    I use [email protected] and use incremental delivery

    You must upgrade to [email protected] to continue using incremental delivery. If you'd like to continue providing support for the legacy incremental protocol, install the @yaacovcr/transform package. Apollo Server will attempt to load this module when the client specifies an Accept header with a value of multipart/mixed; deferSpec=20220824. If this package is not installed, an error is returned by the server.

    Because Apollo Server now supports multiple versions of the incremental delivery types, the existing incremental delivery types have been renamed with an Alpha2 suffix. If you import these types in your code, you will need to add the Alpha2 suffix.

    import type {
- GraphQLExperimentalFormattedInitialIncrementalExecutionResult,
+ GraphQLExperimentalFormattedInitialIncrementalExecutionResultAlpha2,

      

    • GraphQLExperimentalFormattedSubsequentIncrementalExecutionResult,
      • 

    

      

    • GraphQLExperimentalFormattedSubsequentIncrementalExecutionResultAlpha2,
      • 

    

      

    • GraphQLExperimentalFormattedIncrementalResult,
      • 

    

      

    • GraphQLExperimentalFormattedIncrementalResultAlpha2,
      •

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by apollo-bot, a new releaser for @​apollo/server since your current version.


Updates graphql from 16.11.0 to 16.12.0

Release notes

Sourced from graphql's releases.

16.12.0

v16.12.0 (2025-11-01)

New Feature 🚀

Bug Fix 🐞

Docs 📝

Polish 💅

Internal 🏠

... (truncated)

Commits

Updates mercurius from 16.2.0 to 16.6.0

Release notes

Sourced from mercurius's releases.

v16.6.0

What's Changed

Full Changelog: https://github.com/mercurius-js/mercurius/compare/v16.5.0...v16.6.0

v16.5.0

What's Changed

Full Changelog: https://github.com/mercurius-js/mercurius/compare/v16.3.0...v16.5.0

v16.4.0

What's Changed

Full Changelog: https://github.com/mercurius-js/mercurius/compare/v16.3.0...v16.4.0

v16.3.0

What's Changed

New Contributors

Full Changelog: https://github.com/mercurius-js/mercurius/compare/v16.2.0...v16.3.0

Commits

Updates @apollo/server from 4.12.2 to 5.2.0

Release notes

Sourced from @​apollo/server's releases.

@​apollo/server-integration-testsuite@​5.2.0

Patch Changes

  • Updated dependencies [51acbeb]:
    • @​apollo/server@​5.2.0

@​apollo/server@​5.2.0

Minor Changes

  • #8161 51acbeb Thanks @​jerelmiller! - Fix an issue where some bundlers would fail to build because of the dynamic import for the optional peer dependency on @yaacovcr/transform introduced in @apollo/server 5.1.0. To provide support for the legacy incremental format, you must now provide the legacyExperimentalExecuteIncrementally option to the ApolloServer constructor.

    import { legacyExecuteIncrementally } from '@yaacovcr/transform';

    const server = new ApolloServer({
// ...
legacyExperimentalExecuteIncrementally: legacyExecuteIncrementally,
});

    If the legacyExperimentalExecuteIncrementally option is not provided and the client sends an Accept header with a value of multipart/mixed; deferSpec=20220824, an error is returned by the server.

@​apollo/server-integration-testsuite@​5.1.0

Patch Changes

  • Updated dependencies [80a1a1a]:
    • @​apollo/server@​5.1.0

@​apollo/server@​5.1.0

Minor Changes

  • #8148 80a1a1a Thanks @​jerelmiller! - Apollo Server now supports the incremental delivery protocol (@defer and @stream) that ships with [email protected]. To use the current protocol, clients must send the Accept header with a value of multipart/mixed; incrementalSpec=v0.2.

    Upgrading to 5.1 will depend on what version of graphql you have installed and whether you already support the incremental delivery protocol.

    I use graphql@16 without incremental delivery

    Continue using graphql v16 with no additional changes. Incremental delivery won't be available.

    I use graphql@16 but would like to add support for incremental delivery

    Install [email protected] and follow the "Incremental delivery" guide to add the @defer and @stream directives to your schema. Clients should send the Accept header with a value of multipart/mixed; incrementalSpec=v0.2 to get multipart responses.

    I use [email protected] and use incremental delivery

    You must upgrade to [email protected] to continue using incremental delivery. If you'd like to continue providing support for the legacy incremental protocol, install the @yaacovcr/transform package. Apollo Server will attempt to load this module when the client specifies an Accept header with a value of multipart/mixed; deferSpec=20220824. If this package is not installed, an error is returned by the server.

    Because Apollo Server now supports multiple versions of the incremental delivery types, the existing incremental delivery types have been renamed with an Alpha2 suffix. If you import these types in your code, you will need to add the Alpha2 suffix.

... (truncated)

Changelog

Sourced from @​apollo/server's changelog.

5.2.0

Minor Changes

  • #8161 51acbeb Thanks @​jerelmiller! - Fix an issue where some bundlers would fail to build because of the dynamic import for the optional peer dependency on @yaacovcr/transform introduced in @apollo/server 5.1.0. To provide support for the legacy incremental format, you must now provide the legacyExperimentalExecuteIncrementally option to the ApolloServer constructor.

    import { legacyExecuteIncrementally } from '@yaacovcr/transform';

    const server = new ApolloServer({
// ...
legacyExperimentalExecuteIncrementally: legacyExecuteIncrementally,
});

    If the legacyExperimentalExecuteIncrementally option is not provided and the client sends an Accept header with a value of multipart/mixed; deferSpec=20220824, an error is returned by the server.

5.1.0

Minor Changes

  • #8148 80a1a1a Thanks @​jerelmiller! - Apollo Server now supports the incremental delivery protocol (@defer and @stream) that ships with [email protected]. To use the current protocol, clients must send the Accept header with a value of multipart/mixed; incrementalSpec=v0.2.

    Upgrading to 5.1 will depend on what version of graphql you have installed and whether you already support the incremental delivery protocol.

    I use graphql@16 without incremental delivery

    Continue using graphql v16 with no additional changes. Incremental delivery won't be available.

    I use graphql@16 but would like to add support for incremental delivery

    Install [email protected] and follow the "Incremental delivery" guide to add the @defer and @stream directives to your schema. Clients should send the Accept header with a value of multipart/mixed; incrementalSpec=v0.2 to get multipart responses.

    I use [email protected] and use incremental delivery

    You must upgrade to [email protected] to continue using incremental delivery. If you'd like to continue providing support for the legacy incremental protocol, install the @yaacovcr/transform package. Apollo Server will attempt to load this module when the client specifies an Accept header with a value of multipart/mixed; deferSpec=20220824. If this package is not installed, an error is returned by the server.

    Because Apollo Server now supports multiple versions of the incremental delivery types, the existing incremental delivery types have been renamed with an Alpha2 suffix. If you import these types in your code, you will need to add the Alpha2 suffix.

    import type {
- GraphQLExperimentalFormattedInitialIncrementalExecutionResult,
+ GraphQLExperimentalFormattedInitialIncrementalExecutionResultAlpha2,

      

    • GraphQLExperimentalFormattedSubsequentIncrementalExecutionResult,
      • 

    

      

    • GraphQLExperimentalFormattedSubsequentIncrementalExecutionResultAlpha2,
      • 

    

      

    • GraphQLExperimentalFormattedIncrementalResult,
      • 

    

      

    • GraphQLExperimentalFormattedIncrementalResultAlpha2,
      •

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by apollo-bot, a new releaser for @​apollo/server 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

dependabot[bot] avatar Nov 24 '25 12:11 dependabot[bot]