Update all non-major dependencies #33
Open
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.11.3
->4.12.2
2.10.0
->2.11.0
0.49.1
->0.50.1
^0.49.0
->^0.50.0
1.13.5
->1.15.0
1.2.26
->1.2.27
1.5.2
->1.5.5
0.18.1
->0.18.3
8.2.5
->8.2.6
22.14.0
->22.15.29
0.10.5
->0.10.8
0.10.3
->0.10.10
1.13.5
->1.15.0
10.4.17
->10.4.19
16.10.0
->16.11.0
16.10.0
->16.11.0
16.10.0
->16.11.0
5.13.2
->5.13.5
1.68.0
->1.69.0
22.14.0-slim
->22.16.0-slim
4.19.3
->4.19.4
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
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 middlewareapollographql/federation (@apollo/subgraph)
v2.11.0
Compare Source
Minor Changes
Patch Changes
1462c91879d41884c0a7e60551d8dd0d67c832d3
,9614b26e5a17cbf1f6aaf08f6fcb1c95eb12592d
]:v2.10.2
Compare Source
Patch Changes
v2.10.1
Compare Source
Patch Changes
97d81b79c3da10175bdf92c2209039efe352de79
]:graphql-hive/platform (@graphql-hive/cli)
v0.50.1
Compare Source
Patch Changes
[
bbd5643
]:v0.50.0
Compare Source
Minor Changes
#6658
e6a970f
Thanks @n1ru4l! - Internal adjustments for using non-deprecated API
fields.
#6626
2056307
Thanks @jdolle! - Show dangerous changes as a separate list in
schema:check
#6662
2b220a5
Thanks @n1ru4l! - Support federation composition validation for
IMPLEMENTED_BY_INACCESSIBLE
.#6675
ed66171
Thanks @kamilkisiela! - Updates the
@theguild/federation-composition
tov0.18.1
that includes the following changes:@override(label: "<value>")
)@composeDirective
on a built-in scalar (like@oneOf
)600ms)
@shareable
Patch Changes
#6768
5ee3a2e
Thanks @jdolle! - Correct error exit codes
Updated dependencies
[
5130fc1
]:graphql-hive/gateway (@graphql-hive/gateway)
v1.15.0
Compare Source
Minor Changes
dacad53
Thanks @ardatan! - Serve GraphiQL offline by default instead of fetching it from CDNPatch Changes
#1156
fb74009
Thanks @dependabot! - dependencies updates:graphql-yoga@^5.13.5
↗︎ (from^5.13.4
, independencies
)#1158
a5d18da
Thanks @dependabot! - dependencies updates:@commander-js/extra-typings@^14.0.0
↗︎ (from^13.1.0
, independencies
)#1161
3be8206
Thanks @dependabot! - dependencies updates:@commander-js/extra-typings@^13.1.0
↗︎ (from^14.0.0
, independencies
)#1172
dacad53
Thanks @ardatan! - dependencies updates:@graphql-yoga/render-graphiql@^5.13.5
↗︎ (todependencies
)#1182
f3615ca
Thanks @dependabot! - dependencies updates:@graphql-tools/graphql-file-loader@^8.0.20
↗︎ (from^8.0.14
, independencies
)#1141
d8892f2
Thanks @EmrysMyrddin! - Security Update: The Docker image have been updated to fix a CVE affectingpasswd
command. This CVE was not directly affecting Hive Gateway software, since it's not using impacted components.Updated dependencies [
11cff4f
,54beb7a
,fb74009
,f3615ca
,d459f37
,fb74009
,fb74009
,fb74009
,54beb7a
,b4ba778
,11cff4f
]:v1.14.2
Compare Source
Patch Changes
#1113
88c9369
Thanks @ardatan! - Do not print warnings for missinggatewayConfig
export formesh.config
filesUpdated dependencies [
162693e
,4acd5ca
,88c9369
,faffc17
]:v1.14.1
Compare Source
Patch Changes
#1088
305dbc4
Thanks @enisdenjo! - dependencies updates:@graphql-hive/plugin-deduplicate-request@workspace:^
↗︎ (todependencies
)@graphql-mesh/plugin-deduplicate-request@^0.104.0
↗︎ (fromdependencies
)#1088
305dbc4
Thanks @enisdenjo! - Use request deduplication plugin specifically made for Hive GatewayUpdated dependencies [
2dc5fd8
,305dbc4
,305dbc4
,2dc5fd8
]:v1.14.0
Compare Source
Minor Changes
#1083
695251a
Thanks @enisdenjo! - Support watching supergraph file out-of-boxNo extra dependency of
@parcel/watcher
is needed. After upgrading, you can uninstall it.Patch Changes
#1057
20e120b
Thanks @enisdenjo! - dependencies updates:@graphql-mesh/plugin-jwt-auth@workspace:^
↗︎ (from^1.5.0
, independencies
)#1083
695251a
Thanks @enisdenjo! - dependencies updates:@parcel/watcher@^2.1.0
↗︎ (frompeerDependencies
)Updated dependencies [
20e120b
]:v1.13.6
Compare Source
Patch Changes
#1015
9a120c8
Thanks @ardatan! - dependencies updates:graphql-yoga@^5.13.3
↗︎ (from^5.13.2
, independencies
)#1045
da47a0e
Thanks @enisdenjo! - dependencies updates:graphql-yoga@^5.13.4
↗︎ (from^5.13.3
, independencies
)#1045
da47a0e
Thanks @enisdenjo! - Update graphql-yoga and whatwg-node packagesIn light of https://github.com/ardatan/whatwg-node/pull/2305. Please upgrade as soon as possible!
Updated dependencies [
9a120c8
,da47a0e
,da47a0e
,da47a0e
,f797304
,4cf75cb
,0f70298
]:graphql-hive/gateway (@graphql-mesh/hmac-upstream-signature)
v1.2.27
Compare Source
Patch Changes
#1045
da47a0e
Thanks @enisdenjo! - Update graphql-yoga and whatwg-node packagesIn light of https://github.com/ardatan/whatwg-node/pull/2305. Please upgrade as soon as possible!
graphql-hive/gateway (@graphql-mesh/plugin-jwt-auth)
v1.5.5
Compare Source
Patch Changes
#1156
fb74009
Thanks @dependabot! - dependencies updates:@graphql-yoga/plugin-jwt@^3.7.6
↗︎ (from^3.4.9
, independencies
)v1.5.4
Compare Source
Patch Changes
20e120b
Thanks @enisdenjo! - No code changes, the plugin has been moved from Mesh Compose to Hive Gatewayv1.5.3
Compare Source
Patch Changes
#8615
0af3d0c
Thanks @enisdenjo! - Update graphql-yoga and whatwg-node packages
In light of https://github.com/ardatan/whatwg-node/pull/2305. Please upgrade as soon as possible!
Updated dependencies
[
0af3d0c
,0af3d0c
]:graphql-hive/federation-composition (@theguild/federation-composition)
v0.18.3
Compare Source
Patch Changes
bcea968
Thanks @n1ru4l! - Do not throw an error when encountering invalid usage of@tag
directive within subgraphs.v0.18.2
Compare Source
Patch Changes
#141
fdb491f
Thanks @ardatan! - Fixes the issue where the composition gives errors in case of the following:ardatan/whatwg-node (@whatwg-node/fetch)
v0.10.8
Compare Source
Patch Changes
#2424
28c4ad9
Thanks @ardatan! - Performance optimizations
AbortController
andAbortSignal
if not needed withnew Request
because itis expensive
Headers
and try to re-use the init object forHeaders
forperformance with a single-line
writeHead
.Buffer
forstring
bodies for performancesetHeaders
which acceptsHeaders
since Node 18 if needed to forwardHeaders
to NodeUpdated dependencies
[
28c4ad9
]:v0.10.7
Compare Source
Patch Changes
#2383
9527e8f
Thanks @ardatan! - Some implementations like
compression
npmpackage do not implement
response.write(data, callback)
signature, but whatwg-node/server waitsfor it to finish the response stream. Then it causes the response stream hangs when the
compression package takes the stream over when the response data is larger than its threshold.
It is actually a bug in
compression
package;expressjs/compression#46 But since it is a
common mistake, we prefer to workaround this on our end.
Now after calling
response.write
, it no longer uses callback but first it checks the result;if it is
true
, it means stream is drained and we can callresponse.end
immediately. else if itis
false
, it means the stream is not drained yet, so we can wait for thedrain
event to callresponse.end
.Updated dependencies
[
9527e8f
]:v0.10.6
Compare Source
Patch Changes
f699a1b
Thanks @enisdenjo! - dependencies updates:
@whatwg-node/node-fetch@^0.7.18
↗︎(from
^0.7.11
, independencies
)ardatan/whatwg-node (@whatwg-node/server)
v0.10.10
Compare Source
Patch Changes
#2452
19c0be5
Thanks @ardatan! - Support AbortSignal.any on Node.js
#2452
19c0be5
Thanks @ardatan! - Prevent custom AbortSignal to log
"MaxListenersExceededWarning"
v0.10.9
Compare Source
Patch Changes
#2424
28c4ad9
Thanks @ardatan! - Performance optimizations
AbortController
andAbortSignal
if not needed withnew Request
because itis expensive
Headers
and try to re-use the init object forHeaders
forperformance with a single-line
writeHead
.Buffer
forstring
bodies for performancesetHeaders
which acceptsHeaders
since Node 18 if needed to forwardHeaders
to Node1642a76
Thanks @ardatan! - Remove unnecessary workaround for Bun
Updated dependencies
[
28c4ad9
]:v0.10.8
Compare Source
Patch Changes
8eb332c
Thanks @ardatan! - Workaround for the bug in Node 24 and Deno don't
like bound disposal functions
v0.10.7
Compare Source
Patch Changes
085186b
Thanks @renovate! - Fix explicit resource management for Deno
v0.10.6
Compare Source
Patch Changes
#2383
9527e8f
Thanks @ardatan! - Some implementations like
compression
npmpackage do not implement
response.write(data, callback)
signature, but whatwg-node/server waitsfor it to finish the response stream. Then it causes the response stream hangs when the
compression package takes the stream over when the response data is larger than its threshold.
It is actually a bug in
compression
package;expressjs/compression#46 But since it is a
common mistake, we prefer to workaround this on our end.
Now after calling
response.write
, it no longer uses callback but first it checks the result;if it is
true
, it means stream is drained and we can callresponse.end
immediately. else if itis
false
, it means the stream is not drained yet, so we can wait for thedrain
event to callresponse.end
.Updated dependencies
[
d86b4f3
,9527e8f
]:v0.10.5
Compare Source
Patch Changes
b9f3629
Thanks @enisdenjo! - dependencies updates:
@whatwg-node/fetch@^0.10.6
↗︎(from
^0.10.5
, independencies
)v0.10.4
[Compare Source](https://redirect.github.com/ardatan/whatwg-node/compare/@whatwg-node/s
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.