Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 19, 2023

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@apollo/server (source) 4.9.34.12.2 age confidence
@faker-js/faker (source) 8.0.28.4.1 age confidence
@nestjs/apollo 12.0.112.2.2 age confidence
@nestjs/bullmq 10.0.010.2.3 age confidence
@nestjs/cli 10.1.1710.4.9 age confidence
@nestjs/common (source) 10.2.510.4.21 age confidence
@nestjs/config 3.1.13.3.0 age confidence
@nestjs/core (source) 10.2.510.4.21 age confidence
@nestjs/graphql 12.0.112.2.2 age confidence
@nestjs/jwt 10.1.010.2.0 age confidence
@nestjs/platform-express (source) 10.2.510.4.21 age confidence
@nestjs/schematics 10.0.110.2.3 age confidence
@nestjs/testing (source) 10.2.510.4.21 age confidence
@opentelemetry/api (source) 1.6.01.9.0 age confidence
@opentelemetry/auto-instrumentations-node (source) 0.39.20.67.3 age confidence
@opentelemetry/core (source) 1.17.01.30.1 age confidence
@opentelemetry/exporter-jaeger (source) 1.17.01.30.1 age confidence
@opentelemetry/exporter-trace-otlp-http (source) 0.43.00.209.0 age confidence
@opentelemetry/instrumentation (source) 0.43.00.209.0 age confidence
@opentelemetry/resources (source) 1.17.01.30.1 age confidence
@opentelemetry/sdk-node (source) 0.43.00.209.0 age confidence
@opentelemetry/sdk-trace-base (source) 1.17.01.30.1 age confidence
@opentelemetry/sdk-trace-node (source) 1.17.01.30.1 age confidence
@opentelemetry/semantic-conventions (source) 1.17.01.38.0 age confidence
@prisma/client (source) 5.3.15.22.0 age confidence
@prisma/instrumentation (source) 5.3.15.22.0 age confidence
@swc/core (source) 1.3.651.15.8 age confidence
@types/node (source) 18.17.1618.19.130 age confidence
@types/ws (source) 8.5.58.18.1 age confidence
@typescript-eslint/eslint-plugin (source) 6.7.06.21.0 age confidence
@typescript-eslint/parser (source) 6.7.06.21.0 age confidence
bullmq (source) 4.0.04.18.3 age confidence
eslint (source) 8.49.08.57.1 age confidence
eslint-plugin-import 2.28.12.32.0 age confidence
eslint-plugin-prettier 5.0.05.5.4 age confidence
express (source) 4.18.24.22.1 age confidence
firebase-admin (source) 11.10.111.11.1 age confidence
graphql 16.8.016.12.0 age confidence
graphql-redis-subscriptions 2.6.02.7.0 age confidence
graphql-ws (source) 5.13.15.16.2 age confidence
ioredis 5.3.25.9.1 age confidence
passport (source) 0.6.00.7.0 age confidence
prettier (source) 3.0.03.7.4 age confidence
prisma (source) 5.3.15.22.0 age confidence
reflect-metadata (source) 0.1.130.2.2 age confidence
ts-loader 9.4.39.5.4 age confidence
typescript (source) 5.2.25.9.3 age confidence
ulid 2.3.02.4.0 age confidence
unplugin-swc (source) 1.4.21.5.9 age confidence
vite-tsconfig-paths 4.2.04.3.2 age confidence
vitest-mock-extended 1.2.11.3.2 age confidence
ws 8.13.08.19.0 age confidence

Release Notes

apollographql/apollo-server (@​apollo/server)

v4.12.2

Compare Source

(No change; there is a change to the @apollo/server-integration-testsuite used to test integrations, and the two packages always have matching versions.)

v4.12.1

Compare Source

Patch Changes

v4.12.0

Compare Source

Minor Changes
  • #​8054 89e3f84 Thanks @​clenfest! - Adds a new graphql-js validation rule to reject operations that recursively request selections above a specified maximum, which is disabled by default. Use configuration option maxRecursiveSelections=true to enable with a maximum of 10,000,000, or maxRecursiveSelections=<number> for a custom maximum. Enabling this validation can help avoid performance issues with configured validation rules or plugins.
Patch Changes

v4.11.3

Compare Source

Patch Changes

v4.11.2

Compare Source

(No change; there is a change to the @apollo/server-integration-testsuite used to test integrations, and the two packages always have matching versions.)

v4.11.1

Compare Source

Patch Changes
  • #​7952 bb81b2c Thanks @​glasser! - Upgrade dependencies so that automated scans don't detect a vulnerability.

    @apollo/server depends on express which depends on cookie. Versions of express older than v4.21.1 depend on a version of cookie vulnerable to CVE-2024-47764. Users of older express versions who call res.cookie() or res.clearCookie() may be vulnerable to this issue.

    However, Apollo Server does not call this function directly, and it does not expose any object to user code that allows TypeScript users to call this function without an unsafe cast.

    The only way that this direct dependency can cause a vulnerability for users of Apollo Server is if you call startStandaloneServer with a context function that calls Express-specific methods such as res.cookie() or res.clearCookies() on the response object, which is a violation of the TypeScript types provided by startStandaloneServer (which only promise that the response object is a core Node.js http.ServerResponse rather than the Express-specific subclass). So this vulnerability can only affect Apollo Server users who use unsafe JavaScript or unsafe as typecasts in TypeScript.

    However, this upgrade will at least prevent vulnerability scanners from alerting you to this dependency, and we encourage all Express users to upgrade their project's own express dependency to v4.21.1 or newer.

v4.11.0

Compare Source

Minor Changes
  • #​7916 4686454 Thanks @​andrewmcgivery! - Add hideSchemaDetailsFromClientErrors option to ApolloServer to allow hiding 'did you mean' suggestions from validation errors.

    Even with introspection disabled, it is possible to "fuzzy test" a graph manually or with automated tools to try to determine the shape of your schema. This is accomplished by taking advantage of the default behavior where a misspelt field in an operation
    will be met with a validation error that includes a helpful "did you mean" as part of the error text.

    For example, with this option set to true, an error would read Cannot query field "help" on type "Query". whereas with this option set to false it would read Cannot query field "help" on type "Query". Did you mean "hello"?.

    We recommend enabling this option in production to avoid leaking information about your schema to malicious actors.

    To enable, set this option to true in your ApolloServer options:

    const server = new ApolloServer({
      typeDefs,
      resolvers,
      hideSchemaDetailsFromClientErrors: true,
    });

v4.10.5

Compare Source

Patch Changes

v4.10.4

Compare Source

Patch Changes
  • #​7871 18a3827 Thanks @​tninesling! - Subscription heartbeats are initialized prior to awaiting subscribe(). This allows long-running setup to happen in the returned Promise without the subscription being terminated prior to resolution.

v4.10.3

Compare Source

Patch Changes
  • #​7866 5f335a5 Thanks @​tninesling! - Catch errors thrown by subscription generators, and gracefully clean up the subscription instead of crashing.

v4.10.2

Compare Source

Patch Changes
  • #​7849 c7e514c Thanks @​TylerBloom! - In the subscription callback server plugin, terminating a subscription now immediately closes the internal async generator. This avoids that generator existing after termination and until the next message is received.

v4.10.1

Compare Source

Patch Changes
  • #​7843 72f568e Thanks @​bscherlein! - Improves timing of the willResolveField end hook on fields which return Promises resolving to Arrays. This makes the use of the setCacheHint method more reliable.

v4.10.0

Compare Source

Minor Changes
  • #​7786 869ec98 Thanks @​ganemone! - Restore missing v1 skipValidation option as dangerouslyDisableValidation. Note that enabling this option exposes your server to potential security and unexpected runtime issues. Apollo will not support issues that arise as a result of using this option.

  • #​7803 e9a0d6e Thanks @​favna! - allow stringifyResult to return a Promise<string>

    Users who implemented the stringifyResult hook can now expect error responses to be formatted with the hook as well. Please take care when updating to this version to ensure this is the desired behavior, or implement the desired behavior accordingly in your stringifyResult hook. This was considered a non-breaking change as we consider that it was an oversight in the original PR that introduced stringifyResult hook.

Patch Changes

v4.9.5

Compare Source

Patch Changes

v4.9.4

Compare Source

Patch Changes
  • #​7747 ddce036e1 Thanks @​trevor-scheer! - The minimum version of graphql officially supported by Apollo Server 4 as a peer dependency, v16.6.0, contains a serious bug that can crash your Node server. This bug is fixed in the immediate next version, graphql@16.7.0, and we strongly encourage you to upgrade your installation of graphql to at least v16.7.0 to avoid this bug. (For backwards compatibility reasons, we cannot change Apollo Server 4's minimum peer dependency, but will change it when we release Apollo Server 5.)

    Apollo Server 4 contained a particular line of code that makes triggering this crashing bug much more likely. This line was already removed in Apollo Server v3.8.2 (see #​6398) but the fix was accidentally not included in Apollo Server 4. We are now including this change in Apollo Server 4, which will reduce the likelihood of hitting this crashing bug for users of graphql v16.6.0. That said, taking this @apollo/server upgrade does not prevent this bug from being triggered in other ways, and the real fix to this crashing bug is to upgrade graphql.

faker-js/faker (@​faker-js/faker)

v8.4.1

Compare Source

  • JSDocs improvements

v8.4.0

Compare Source

Features
Bug Fixes
8.3.1 (2023-11-14)
Bug Fixes
  • remove [@internal](https://redirect.github.com/internal) from module parent classes (#​2548) (77f54ad)

v8.3.1

Compare Source

v8.3.0

Compare Source

Features
Bug Fixes
Changed Locales
New Locales

v8.2.0

Compare Source

Features
Bug Fixes
New Locales

v8.1.0

Compare Source

Features
Bug Fixes
Changed Locales
New Locales
8.0.2 (2023-05-27)
Bug Fixes
  • git: limit need for Intl to specific method ([#&#8203

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from f1d7514 to df3fa70 Compare September 26, 2023 12:18
@renovate renovate bot force-pushed the renovate/all branch 8 times, most recently from 3bcd816 to 32aea61 Compare October 5, 2023 00:45
@renovate renovate bot force-pushed the renovate/all branch 8 times, most recently from 839a8e4 to fb748ac Compare October 12, 2023 23:16
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 88d53c7 to 84a8c47 Compare October 18, 2023 13:10
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from a0b82ed to 2f05cde Compare October 23, 2023 18:49
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from 43dd13a to 0da51e4 Compare November 6, 2025 19:40
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from a0e67f2 to 3fe2de2 Compare November 14, 2025 22:09
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from cb7ff51 to d896383 Compare November 24, 2025 17:48
@renovate renovate bot force-pushed the renovate/all branch 8 times, most recently from 4ec870a to 347bfb3 Compare December 3, 2025 19:04
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from d4aaf61 to 43850b5 Compare December 18, 2025 18:41
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 57beb20 to 3a8a9f8 Compare January 5, 2026 21:43
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from a20f8b6 to 5fd2301 Compare January 8, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant