fix(deps): update all major dependencies (major) #74
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.10.0->5.0.02.1.1->3.1.06.12.0->8.3.029.7.0->30.2.029.6.3->30.2.05.9.8->6.5.85.9.8->6.5.85.9.8->6.5.85.2.3->6.1.15.9.8->6.5.812.1.0->13.2.110.3.3->11.1.610.3.3->11.1.610.2.7->11.0.312.1.1->13.2.010.3.3->11.1.610.3.3->11.1.67.3.0->11.2.120.11.24->22.18.116.21.0->8.46.16.21.0->8.46.1v4->v5v4->v6v3->v5v5->v616.4.5->17.2.38.57.0->9.38.03.6.1->4.4.427.9.0->29.0.18.0.3->9.1.729.7.0->30.2.015.2.2->16.2.4v2.4.0->v4.2.05.0.5->6.0.11.12.4->2.5.8Release Notes
apollographql/apollo-server (@apollo/server)
v5.0.0Compare Source
BREAKING CHANGES
Apollo Server v5 has very few breaking API changes. It is a small upgrade focused largely on adjusting which versions of Node.js and Express are supported.
Read our migration guide for more details on how to update your app.
graphqllibrary older thanv16.11.0. (Apollo Server 4 supportsgraphqlv16.6.0or later.) Upgradegraphqlbefore upgrading Apollo Server.@apollo/server/express4, or you could import it from the separate package@as-integrations/express4. In Apollo Server 5, you must import it from the separate package. You can migrate your server to the new package before upgrading to Apollo Server 5. (You can also use@as-integrations/express5for a middleware that works with Express 5.)fetchimplementation for HTTP requests by default, instead of thenode-fetchnpm package. If your server uses an HTTP proxy to make HTTP requests, you need to configure it in a slightly different way. See the migration guide for details.startStandaloneServerno longer uses Express. This is mostly invisible, but it does set slightly fewer headers. If you rely on the fact that this server is based on Express, you should explicitly use the Express middleware.@deferand@stream(which requires using a pre-release version ofgraphqlv17) now explicitly only works with version17.0.0-alpha.2ofgraphql. Note that this supports the same incremental delivery protocol implemented by Apollo Server 4, which is not the same protocol in the latest alpha version ofgraphql. As this support is experimental, we may switch over from "onlyalpha.2is supported" to "only a newer alpha or final release is supported, with a different protocol" during the lifetime of Apollo Server 5.variablesmap for a variable declared in the operation as aString) with a 400 status code, indicating a client error. This is also the behavior of Apollo Server 3. Apollo Server 4 mistakenly responds to these requests with a 200 status code by default; we recommended the use of thestatus400ForVariableCoercionErrors: trueoption to restore the intended behavior. That option now defaults to true.precomputedNonceoption to landing page plugins (which was only non-deprecated for 8 days) has been removed.Patch Changes
There are a few other small changes in v5:
#8076
5b26558Thanks @valters! - Fix some error logs to properly calllogger.errororlogger.warnwiththisset. This fixes errors or crashes from logger implementations that expectthisto be set properly in their methods.#7515
100233aThanks @trevor-scheer! - ApolloServerPluginSubscriptionCallback now takes afetcherargument, like the usage and schema reporting plugins. The default value is Node's built-in fetch.Updated dependencies [
100233a]: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.apollo-server-integrations/apollo-server-integration-fastify (@as-integrations/fastify)
v3.1.0Compare Source
Changes
v3.0.0Compare Source
-- BREAKING: Requires Node >= 20
-- BREAKING: Requires Typescript >= 5.4
-- FEATURE: Update to support fastify v5 #302
fastify/fastify-static (@fastify/static)
v8.3.0Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-static@v8.2.0...v8.3.0
v8.2.0Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-static@v8.1.1...v8.2.0
v8.1.1Compare Source
What's Changed
preCompressedby @genki in #509New Contributors
Full Changelog: fastify/fastify-static@v8.1.0...v8.1.1
v8.1.0Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-static@v8.0.4...v8.1.0
v8.0.4Compare Source
What's Changed
node:prefix for builtins by @Fdawgs in #490New Contributors
Full Changelog: fastify/fastify-static@v8.0.3...v8.0.4
v8.0.3Compare Source
What's Changed
contentTypesend option by @Fdawgs in #484New Contributors
Full Changelog: fastify/fastify-static@v8.0.2...v8.0.3
v8.0.2Compare Source
What's Changed
Full Changelog: fastify/fastify-static@v8.0.1...v8.0.2
v8.0.1Compare Source
What's Changed
Full Changelog: fastify/fastify-static@v8.0.0...v8.0.1
v8.0.0Compare Source
What's Changed
nextintomasterby @jsumners in #454Full Changelog: fastify/fastify-static@v7.0.4...v8.0.0
v7.0.4Compare Source
What's Changed
%in filename by @chetbox in #452New Contributors
Full Changelog: fastify/fastify-static@v7.0.3...v7.0.4
v7.0.3Compare Source
What's Changed
Full Changelog: fastify/fastify-static@v7.0.2...v7.0.3
v7.0.2Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-static@v7.0.1...v7.0.2
v7.0.1Compare Source
What's Changed
dirListby @gurgunday in #435Full Changelog: fastify/fastify-static@v7.0.0...v7.0.1
v7.0.0Compare Source
What's Changed
fastify.iolinks withfastify.devby @Fdawgs in #425fastify.iolinks withfastify.devby @Fdawgs in #426setHeadersoption by @EvanHahn in #428New Contributors
Full Changelog: fastify/fastify-static@v6.12.0...v7.0.0
jestjs/jest (@jest/globals)
v30.2.0Compare Source
Chore & Maintenance
[*]Update example repo for testing React Native projects (#15832)[*]Updatejest-watch-typeaheadto v3 (#15830)v30.1.2Compare Source
Fixes
[jest-snapshot-utils]Correct snapshot header regexp to work with newline across OSes (#15803)v30.1.1Compare Source
Fixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#15800)[jest-snapshot-utils]Improve messaging about goo.gl snapshot link change (#15821)[
v30.1.0](https://redirect.github.com/jestjs/jest/blConfiguration
📅 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 is behind base branch, 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.