-
Notifications
You must be signed in to change notification settings - Fork 0
fix(deps): update all major dependencies (major) #74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-all-major-dependencies
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+157
−157
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
92cc168
to
132f1f3
Compare
168e9fa
to
d84e471
Compare
68316ef
to
ce0d625
Compare
ce0d625
to
10dc814
Compare
8acca9c
to
1cdda7f
Compare
a01f85d
to
68d568a
Compare
68d568a
to
4642f27
Compare
06eb434
to
280111a
Compare
4659881
to
00cedb4
Compare
00cedb4
to
7753174
Compare
1067cb7
to
e17b0e2
Compare
fb78cdd
to
cf690a0
Compare
cf690a0
to
682099c
Compare
682099c
to
7fe9039
Compare
f1e8138
to
3070479
Compare
3070479
to
31cdfc5
Compare
3912932
to
1cd6581
Compare
b335e99
to
8f5dc85
Compare
8f5dc85
to
91dcbcf
Compare
91dcbcf
to
f970649
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.0
2.1.1
->3.0.0
6.12.0
->8.2.0
29.7.0
->30.0.5
29.6.3
->30.0.5
5.9.8
->6.4.16
5.9.8
->6.4.16
5.9.8
->6.4.16
5.2.3
->6.1.1
5.9.8
->6.4.16
12.1.0
->13.1.0
10.3.3
->11.1.6
10.3.3
->11.1.6
10.2.7
->11.0.3
12.1.1
->13.1.0
10.3.3
->11.1.6
10.3.3
->11.1.6
7.3.0
->11.2.0
20.11.24
->22.17.2
6.21.0
->8.40.0
6.21.0
->8.40.0
v4
->v5
v3
->v5
v5
->v6
16.4.5
->17.2.1
8.57.0
->9.34.0
3.6.1
->4.4.4
27.9.0
->29.0.1
8.0.3
->9.1.7
29.7.0
->30.0.5
15.2.2
->16.1.5
v2.4.0
->v4.1.0
5.0.5
->6.0.1
1.12.4
->2.5.6
Release Notes
apollographql/apollo-server (@apollo/server)
v5.0.0
Compare 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.
graphql
library older thanv16.11.0
. (Apollo Server 4 supportsgraphql
v16.6.0
or later.) Upgradegraphql
before 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/express5
for a middleware that works with Express 5.)fetch
implementation for HTTP requests by default, instead of thenode-fetch
npm 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.startStandaloneServer
no 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.@defer
and@stream
(which requires using a pre-release version ofgraphql
v17) now explicitly only works with version17.0.0-alpha.2
ofgraphql
. 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.2
is supported" to "only a newer alpha or final release is supported, with a different protocol" during the lifetime of Apollo Server 5.variables
map 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: true
option to restore the intended behavior. That option now defaults to true.precomputedNonce
option 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
5b26558
Thanks @valters! - Fix some error logs to properly calllogger.error
orlogger.warn
withthis
set. This fixes errors or crashes from logger implementations that expectthis
to be set properly in their methods.#7515
100233a
Thanks @trevor-scheer! - ApolloServerPluginSubscriptionCallback now takes afetcher
argument, like the usage and schema reporting plugins. The default value is Node's built-in fetch.Updated dependencies [
100233a
]: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
41f98d4
Thanks @glasser! - Update README.md to recommend Express v5 integration now that Express v5 is released.v4.12.0
Compare Source
Minor Changes
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 optionmaxRecursiveSelections=true
to 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
2550d9f
Thanks @slagiewka! - Add return after sending 400 response in doubly escaped JSON parser middlewarev4.11.3
Compare Source
Patch Changes
f4228e8
Thanks @glasser! - Compatibility with Next.js Turbopack. Fixes #8004.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 onexpress
which depends oncookie
. Versions ofexpress
older than v4.21.1 depend on a version ofcookie
vulnerable to CVE-2024-47764. Users of olderexpress
versions 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
startStandaloneServer
with 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.ServerResponse
rather than the Express-specific subclass). So this vulnerability can only affect Apollo Server users who use unsafe JavaScript or unsafeas
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! - AddhideSchemaDetailsFromClientErrors
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 readCannot query field "help" on type "Query".
whereas with this option set tofalse
it 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
true
in yourApolloServer
options:v4.10.5
Compare Source
Patch Changes
#7821
b2e15e7
Thanks @renovate! - Non-major dependency updates#7900
86d7111
Thanks @trevor-scheer! - Inline a small dependency that was causing build issues for ESM projectsv4.10.4
Compare Source
Patch Changes
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
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
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
72f568e
Thanks @bscherlein! - Improves timing of thewillResolveField
end hook on fields which return Promises resolving to Arrays. This makes the use of thesetCacheHint
method more reliable.apollo-server-integrations/apollo-server-integration-fastify (@as-integrations/fastify)
v3.0.0
Compare Source
-- BREAKING: Requires Node >= 20
-- BREAKING: Requires Typescript >= 5.4
-- FEATURE: Update to support fastify v5 #302
fastify/fastify-static (@fastify/static)
v8.2.0
Compare Source
v8.1.1
Compare Source
What's Changed
preCompressed
by @genki in https://github.com/fastify/fastify-static/pull/509New Contributors
Full Changelog: fastify/fastify-static@v8.1.0...v8.1.1
v8.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-static@v8.0.4...v8.1.0
v8.0.4
Compare Source
What's Changed
node:
prefix for builtins by @Fdawgs in https://github.com/fastify/fastify-static/pull/490New Contributors
Full Changelog: fastify/fastify-static@v8.0.3...v8.0.4
v8.0.3
Compare Source
What's Changed
contentType
send option by @Fdawgs in https://github.com/fastify/fastify-static/pull/484New Contributors
Full Changelog: fastify/fastify-static@v8.0.2...v8.0.3
v8.0.2
Compare Source
What's Changed
Full Changelog: fastify/fastify-static@v8.0.1...v8.0.2
v8.0.1
Compare Source
What's Changed
Full Changelog: fastify/fastify-static@v8.0.0...v8.0.1
v8.0.0
Compare Source
What's Changed
next
intomaster
by @jsumners in https://github.com/fastify/fastify-static/pull/454Full Changelog: fastify/fastify-static@v7.0.4...v8.0.0
v7.0.4
Compare Source
What's Changed
%
in filename by @chetbox in https://github.com/fastify/fastify-static/pull/452New Contributors
Full Changelog: fastify/fastify-static@v7.0.3...v7.0.4
v7.0.3
Compare Source
What's Changed
Full Changelog: fastify/fastify-static@v7.0.2...v7.0.3
v7.0.2
Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-static@v7.0.1...v7.0.2
v7.0.1
Compare Source
What's Changed
dirList
by @gurgunday in https://github.com/fastify/fastify-static/pull/435Full Changelog: fastify/fastify-static@v7.0.0...v7.0.1
v7.0.0
Compare Source
What's Changed
fastify.io
links withfastify.dev
by @Fdawgs in https://github.com/fastify/fastify-static/pull/425fastify.io
links withfastify.dev
by @Fdawgs in https://github.com/fastify/fastify-static/pull/426setHeaders
option by @EvanHahn in https://github.com/fastify/fastify-static/pull/428New Contributors
Full Changelog: fastify/fastify-static@v6.12.0...v7.0.0
jestjs/jest (@jest/globals)
v30.0.5
Compare Source
Features
[jest-config]
AllowtestMatch
to take a string value[jest-worker]
LetworkerIdleMemoryLimit
accept 0 to always restart worker child processesFixes
[expect]
Fixbigint
error (#15702)v30.0.4
Compare Source
Features
[expect]
TheInverse
type is now exported (#15714)[expect]
feat: supportasync functions
intoBe
(#15704)Fixes
[jest]
jest --onlyFailures --listTests now correctly lists only failed tests (#15700)[jest-snapshot]
Handle line endings in snapshots (#15708)v30.0.3
Compare Source
Fixes
[jest-config]
Fix ESM TS config loading in a CJS project (#15694)[jest-core]
jest --onlyFailures --listTests now correctly lists only failed tests(#15700)Features
[jest-diff]
Show non-printable control characters to diffs (#15696)v30.0.2
Compare Source
Fixes
[jest-matcher-utils]
Make 'deepCyclicCopyObject' safer by setting descriptors to a null-prototype object (#15689)[jest-util]
Make garbage collection protection property writable (#15689)v30.0.1
Compare Source
Features
[jest-resolver]
Implement thedefaultAsyncResolver
(#15679)Fixes
[jest-resolver]
Resolve builtin modules correctly (#15683)[jest-environment-node, jest-util]
Avoid setting globals cleanup protection symbol when feature is off (#15684)Chore & Maintenance
[*]
Remove and deprecatejest-repl
package (#15673)[jest-resolver]
Replace customisBuiltinModule
with node'sisBuiltin
(#15685)v30.0.0
Compare Source
Features
[*]
RenamedglobalsCleanupMode
toglobalsCleanup
and--waitNextEventLoopTurnForUnhandledRejectionEvents
to--waitForUnhandledRejections
[expect]
AddArrayOf
asymmetric matcher for validating array elements. (#15567)[babel-jest]
Add optionexcludeJestPreset
to allow opting out ofbabel-preset-jest
(#15164)[expect]
Revert #15038 to fixexpect(fn).toHaveBeenCalledWith(expect.objectContaining(...))
when there are multiple calls (#15508)[jest-circus, jest-cli, jest-config]
AddwaitNextEventLoopTurnForUnhandledRejectionEvents
flag to minimise performance impact of correct detection of unhandled promise rejections introduced in #14315 (#14681)[jest-circus]
Add awaitBeforeRetry
option tojest.retryTimes
(#14738)[jest-circus]
Add aretryImmediately
option tojest.retryTimes
(#14696)[jest-circus, jest-jasmine2]
AllowsetupFilesAfterEnv
to export an async function (#10962)[jest-circus, jest-test-result]
AddstartedAt
timestamp inTestCaseResultObject
withinonTestCaseResult
(#15145)[jest-cli]
ExportbuildArgv
(#15310)[jest-config]
[BREAKING] Addmts
andcts
to defaultmoduleFileExtensions
config (#14369)[jest-config]
[BREAKING] UpdatetestMatch
andtestRegex
default option for supportingmjs
,cjs
,mts
, andcts
(#14584)[jest-config]
Loads config file from provided path inpackage.json
(#14044)[jest-config]
Allow loadingjest.config.cts
files (#14070)[jest-config]
ShowrootDir
in error message when apreset
fails to load (#15194)[jest-config]
Support loading TS config files usingesbuild-register
via docblock loader ([#15190](https://redirect.giConfiguration
📅 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.