Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.9.3→4.12.28.0.2→8.4.112.0.1→12.2.210.0.0→10.2.310.1.17→10.4.910.2.5→10.4.213.1.1→3.3.010.2.5→10.4.2112.0.1→12.2.210.1.0→10.2.010.2.5→10.4.2110.0.1→10.2.310.2.5→10.4.211.6.0→1.9.00.39.2→0.67.31.17.0→1.30.11.17.0→1.30.10.43.0→0.209.00.43.0→0.209.01.17.0→1.30.10.43.0→0.209.01.17.0→1.30.11.17.0→1.30.11.17.0→1.38.05.3.1→5.22.05.3.1→5.22.01.3.65→1.15.818.17.16→18.19.1308.5.5→8.18.16.7.0→6.21.06.7.0→6.21.04.0.0→4.18.38.49.0→8.57.12.28.1→2.32.05.0.0→5.5.44.18.2→4.22.111.10.1→11.11.116.8.0→16.12.02.6.0→2.7.05.13.1→5.16.25.3.2→5.9.10.6.0→0.7.03.0.0→3.7.45.3.1→5.22.00.1.13→0.2.29.4.3→9.5.45.2.2→5.9.32.3.0→2.4.01.4.2→1.5.94.2.0→4.3.21.2.1→1.3.28.13.0→8.19.0Release Notes
apollographql/apollo-server (@apollo/server)
v4.12.2Compare Source
(No change; there is a change to the
@apollo/server-integration-testsuiteused to test integrations, and the two packages always have matching versions.)v4.12.1Compare Source
Patch Changes
41f98d4Thanks @glasser! - Update README.md to recommend Express v5 integration now that Express v5 is released.v4.12.0Compare Source
Minor Changes
89e3f84Thanks @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 optionmaxRecursiveSelections=trueto enable with a maximum of 10,000,000, ormaxRecursiveSelections=<number>for a custom maximum. Enabling this validation can help avoid performance issues with configured validation rules or plugins.Patch Changes
2550d9fThanks @slagiewka! - Add return after sending 400 response in doubly escaped JSON parser middlewarev4.11.3Compare Source
Patch Changes
f4228e8Thanks @glasser! - Compatibility with Next.js Turbopack. Fixes #8004.v4.11.2Compare Source
(No change; there is a change to the
@apollo/server-integration-testsuiteused to test integrations, and the two packages always have matching versions.)v4.11.1Compare Source
Patch Changes
#7952
bb81b2cThanks @glasser! - Upgrade dependencies so that automated scans don't detect a vulnerability.@apollo/serverdepends onexpresswhich depends oncookie. Versions ofexpressolder than v4.21.1 depend on a version ofcookievulnerable to CVE-2024-47764. Users of olderexpressversions who callres.cookie()orres.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
startStandaloneServerwith a context function that calls Express-specific methods such asres.cookie()orres.clearCookies()on the response object, which is a violation of the TypeScript types provided bystartStandaloneServer(which only promise that the response object is a core Node.jshttp.ServerResponserather than the Express-specific subclass). So this vulnerability can only affect Apollo Server users who use unsafe JavaScript or unsafeastypecasts 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
expressdependency to v4.21.1 or newer.v4.11.0Compare Source
Minor Changes
#7916
4686454Thanks @andrewmcgivery! - AddhideSchemaDetailsFromClientErrorsoption 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 readCannot query field "help" on type "Query".whereas with this option set tofalseit would readCannot 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
truein yourApolloServeroptions:v4.10.5Compare Source
Patch Changes
#7821
b2e15e7Thanks @renovate! - Non-major dependency updates#7900
86d7111Thanks @trevor-scheer! - Inline a small dependency that was causing build issues for ESM projectsv4.10.4Compare Source
Patch Changes
18a3827Thanks @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.3Compare Source
Patch Changes
5f335a5Thanks @tninesling! - Catch errors thrown by subscription generators, and gracefully clean up the subscription instead of crashing.v4.10.2Compare Source
Patch Changes
c7e514cThanks @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.1Compare Source
Patch Changes
72f568eThanks @bscherlein! - Improves timing of thewillResolveFieldend hook on fields which return Promises resolving to Arrays. This makes the use of thesetCacheHintmethod more reliable.v4.10.0Compare Source
Minor Changes
#7786
869ec98Thanks @ganemone! - Restore missing v1skipValidationoption asdangerouslyDisableValidation. 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
e9a0d6eThanks @favna! - allowstringifyResultto return aPromise<string>Users who implemented the
stringifyResulthook 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 yourstringifyResulthook. This was considered a non-breaking change as we consider that it was an oversight in the original PR that introducedstringifyResulthook.Patch Changes
#7793
9bd7748Thanks @bnjjj! - General availability of subscription callback protocol#7799
63dc50fThanks @stijnbe! - Fix type of ApolloServerPluginUsageReporting reportTimer#7740
fe68c1bThanks @barnisanov! - Uninstalledbody-parserand usedexpressbuilt-inbody-parserfunctionality instead(mainly the json middleware)v4.9.5Compare Source
Patch Changes
#7741
07585fe39Thanks @mayakoneval! - Pin major releases of embeddable Explorer & Sandbox code.#7769
4fac1628cThanks @cwikla! - Change SchemaReporter.pollTimer from being a NodeJS.Timer to a NodeJS.Timeoutv4.9.4Compare Source
Patch Changes
#7747
ddce036e1Thanks @trevor-scheer! - The minimum version ofgraphqlofficially 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 ofgraphqlto 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
graphqlv16.6.0. That said, taking this@apollo/serverupgrade does not prevent this bug from being triggered in other ways, and the real fix to this crashing bug is to upgradegraphql.faker-js/faker (@faker-js/faker)
v8.4.1Compare Source
v8.4.0Compare Source
Features
fractionDigitsin float (#1855) (41d8778)Bug Fixes
8.3.1 (2023-11-14)
Bug Fixes
[@internal](https://redirect.github.com/internal)from module parent classes (#2548) (77f54ad)v8.3.1Compare Source
v8.3.0Compare Source
Features
Bug Fixes
Changed Locales
New Locales
v8.2.0Compare Source
Features
Bug Fixes
New Locales
en_US,en_GBanden(#2371) (491d319)v8.1.0Compare Source
Features
Bug Fixes
jalocale (#2189) (785a38a)Changed Locales
New Locales
8.0.2 (2023-05-27)
Bug Fixes
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.
This PR was generated by Mend Renovate. View the repository job log.