-
Notifications
You must be signed in to change notification settings - Fork 4
Update all non-major dependencies #218
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
Merged
Merged
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
d3b204e to
9c240cc
Compare
9c240cc to
5aa2678
Compare
5aa2678 to
2d9ed3e
Compare
2d9ed3e to
3de20f4
Compare
3de20f4 to
2e5f645
Compare
2e5f645 to
3621d0d
Compare
3621d0d to
07fb3e2
Compare
c5b477f to
1a8992a
Compare
ardatan
approved these changes
Nov 10, 2025
04095dd to
ab1afd5
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:
2.11.3->2.12.02.11.3->2.12.05.0.0->5.1.02.11.3->2.12.05.0.3->5.0.517.0.33->17.0.3416.11.0->16.12.05.16.0->5.16.29.0.1->9.0.30.94.0->0.94.5Release Notes
apollographql/federation (@apollo/composition)
v2.12.0Compare Source
Minor Changes
Federation 2.12 and Connect 0.3 (#3276)
Added isSuccess argument to @connect and @source (#3294)
Fixes a bug where composition may not generate a satisfiability error for an unsatisfiable
@shareablemutation field. (#3305) (#3305)Automatically propagate authorization requirements from implementing type to interface in the supergraph. (#3321)
Authorization requirements now automatically propagate from implementing types to interfaces during composition. Direct auth specifications on interfaces are no longer allowed. Interface access requires satisfying ALL implementing types' requirements (
ANDrule), with these requirements included in the supergraph for backward compatibility with older routers.Fix transitive auth requirements on
@requiresand@fromcontext(#3321)Adds new
postMergeValidationcheck to ensure that all fields that depends on data from other parts of the supergraph through@requiresand/or@fromContextdirectives explicitly specify matching@authenticated,@requiresScopesand/or@policyauth requirements, e.g.Adding new CompositionOption
maxValidationSubgraphPaths. This value represents the maximum number of SubgraphPathInfo objects that may exist in a ValidationTraversal when checking for satisfiability. Setting this value can help composition error before running out of memory. Default is 1,000,000. (#3275)Restrict usage of auth directives on interfaces (#3321)
Restricts usage of
@authenticated,@policyand@requiresScopesfrom being applied on interfaces, interface objects and their fields.GraphQL spec currently does not define any interface inheritance rules and developers have to explicitly redefine all interface fields on their implementations. At runtime, GraphQL servers cannot return abstract types and always return concrete output types. Due to the above, applying auth directives on the interfaces may lead to unexpected runtime behavior as they won't have any effect at runtime.
Stricter merge rules for @requiresScopes and @policy (#3321)
Current merge policies for
@authenticated,@requiresScopesand@policywere inconsistent.If a shared field uses the same authorization directives across subgraphs, composition merges them using
ORlogic. However, if a shared field uses different authorization directives across subgraphs composition merges them usingANDlogic. This simplified schema evolution, but weakened security requirements. Therefore, the behavior has been changed to always applyANDlogic to authorization directives applied to the same field across subgraphs.Since
@policyand@requiresScopesvalues represent boolean conditions in Disjunctive Normal Form, we can merge them conjunctively to get the final auth requirements. For example:This algorithm also deduplicates redundant requirements, e.g.
Fixed handling
@requiresdependency on fields returned by@interfaceObject(#3318)Depending on the merge order of the types, we could fail composition if a type that
@requiresdata from an@interfaceObjectis merged before the interface. Updated merge logic to use explicit merge order of scalars, input objects, interfaces, and finally objects.Added preview
@cacheTagdirective support (#3274)Patch Changes
3e2b0a8569a9fe46726182887ed0b4bfc0b52468,bb4614d338ae03bac51a5fc2439590f172c4e54d,99f2da21de88f9ad9a32ee7ed64b2d4a92887b40,468f27842608f4e390cfc88bc7e6b4b0945f95ff,3fd5157b309f1d3439b2d87c67b0601fb246d04c,b734ea04d118db09cf6077fdd968c8f04a96327a,4bda3a498eba36e187dfd9ae673eca12d3f3502c,e7e67579908d5cd2fa6fe558228dffe4808cd98d,f3ab499eaf62b1a1c0f08b838d2cbde5accb303a,faea2d1174d80593264f2227cfde9a2ba1a59b96,97b9d2edfcfeed99124f9e115f992cbef3804682,f6af504f1ba8283fd00af0d6e3c9c1a665d62736,a595235d3cf8f67611efd8395332b64d067b5f1f]:v2.11.4Compare Source
Patch Changes
Automatically propagate authorization requirements from implementing type to interface in the supergraph. (#3325)
Authorization requirements now automatically propagate from implementing types to interfaces during composition. Direct auth specifications on interfaces are no longer allowed. Interface access requires satisfying ALL implementing types' requirements (
ANDrule), with these requirements included in the supergraph for backward compatibility with older routers.Fix transitive auth requirements on
@requiresand@fromcontext(#3325)Adds new
postMergeValidationcheck to ensure that all fields that depends on data from other parts of the supergraph through@requiresand/or@fromContextdirectives explicitly specify matching@authenticated,@requiresScopesand/or@policyauth requirements, e.g.Restrict usage of auth directives on interfaces (#3325)
Restricts usage of
@authenticated,@policyand@requiresScopesfrom being applied on interfaces, interface objects and their fields.GraphQL spec currently does not define any interface inheritance rules and developers have to explicitly redefine all interface fields on their implementations. At runtime, GraphQL servers cannot return abstract types and always return concrete output types. Due to the above, applying auth directives on the interfaces may lead to unexpected runtime behavior as they won't have any effect at runtime.
Stricter merge rules for
@requiresScopesand@policy(#3325)Current merge policies for
@authenticated,@requiresScopesand@policywere inconsistent.If a shared field uses the same authorization directives across subgraphs, composition merges them using
ORlogic. However, if a shared field uses different authorization directives across subgraphs composition merges them usingANDlogic. This simplified schema evolution, but weakened security requirements. Therefore, the behavior has been changed to always applyANDlogic to authorization directives applied to the same field across subgraphs.Since
@policyand@requiresScopesvalues represent boolean conditions in Disjunctive Normal Form, we can merge them conjunctively to get the final auth requirements. For example:This algorithm also deduplicates redundant requirements, e.g.
Updated dependencies [
d221ac04c3ee00a3c7a671d9d56e2cfa36943b49,7730c03e128be6754b9e40c086d5cb5c4685ac66,4bda3a498eba36e187dfd9ae673eca12d3f3502c,f3ab499eaf62b1a1c0f08b838d2cbde5accb303a,6adbf7e86927de969aedab665b6a3a8dbf3a6095,2a20dc38dfc40e0b618d5cc826f18a19ddb91aff]:apollographql/federation (@apollo/gateway)
v2.12.0Compare Source
Minor Changes
Patch Changes
3e2b0a8569a9fe46726182887ed0b4bfc0b52468,bb4614d338ae03bac51a5fc2439590f172c4e54d,99f2da21de88f9ad9a32ee7ed64b2d4a92887b40,468f27842608f4e390cfc88bc7e6b4b0945f95ff,3fd5157b309f1d3439b2d87c67b0601fb246d04c,b734ea04d118db09cf6077fdd968c8f04a96327a,4bda3a498eba36e187dfd9ae673eca12d3f3502c,e7e67579908d5cd2fa6fe558228dffe4808cd98d,f3ab499eaf62b1a1c0f08b838d2cbde5accb303a,faea2d1174d80593264f2227cfde9a2ba1a59b96,0dbc7cc72ffacf324231e9ccb2de4189f6bf3289,97b9d2edfcfeed99124f9e115f992cbef3804682,f6af504f1ba8283fd00af0d6e3c9c1a665d62736,bc07e979b9fd24c9b94740b170f11023fe99ba1e,a595235d3cf8f67611efd8395332b64d067b5f1f,9cbdcb53f859c877a476e2725faa4cb205506f57]:v2.11.4Compare Source
Patch Changes
d221ac04c3ee00a3c7a671d9d56e2cfa36943b49,7730c03e128be6754b9e40c086d5cb5c4685ac66,4bda3a498eba36e187dfd9ae673eca12d3f3502c,f3ab499eaf62b1a1c0f08b838d2cbde5accb303a,6adbf7e86927de969aedab665b6a3a8dbf3a6095,2a20dc38dfc40e0b618d5cc826f18a19ddb91aff]:apollographql/apollo-server (@apollo/server)
v5.1.0Compare Source
Minor Changes
#8148
80a1a1aThanks @jerelmiller! - Apollo Server now supports the incremental delivery protocol (@deferand@stream) that ships with[email protected]. To use the current protocol, clients must send theAcceptheader with a value ofmultipart/mixed; incrementalSpec=v0.2.Upgrading to 5.1 will depend on what version of
graphqlyou have installed and whether you already support the incremental delivery protocol.apollographql/federation (@apollo/subgraph)
v2.12.0Compare Source
Minor Changes
Patch Changes
When a
GraphQLScalarTyperesolver is provided tobuildSubgraphSchema(), omitted configuration options in theGraphQLScalarTypeno longer cause the corresponding properties in the GraphQL document/AST to be cleared. To explicitly clear these properties, usenullfor the configuration option instead. (#3287)Updated dependencies [
3e2b0a8569a9fe46726182887ed0b4bfc0b52468,bb4614d338ae03bac51a5fc2439590f172c4e54d,99f2da21de88f9ad9a32ee7ed64b2d4a92887b40,468f27842608f4e390cfc88bc7e6b4b0945f95ff,3fd5157b309f1d3439b2d87c67b0601fb246d04c,b734ea04d118db09cf6077fdd968c8f04a96327a,4bda3a498eba36e187dfd9ae673eca12d3f3502c,e7e67579908d5cd2fa6fe558228dffe4808cd98d,faea2d1174d80593264f2227cfde9a2ba1a59b96,97b9d2edfcfeed99124f9e115f992cbef3804682,f6af504f1ba8283fd00af0d6e3c9c1a665d62736,a595235d3cf8f67611efd8395332b64d067b5f1f]:v2.11.4Compare Source
Patch Changes
d221ac04c3ee00a3c7a671d9d56e2cfa36943b49,7730c03e128be6754b9e40c086d5cb5c4685ac66,4bda3a498eba36e187dfd9ae673eca12d3f3502c,6adbf7e86927de969aedab665b6a3a8dbf3a6095,2a20dc38dfc40e0b618d5cc826f18a19ddb91aff]:graphql/graphql-js (graphql)
v16.12.0: 16.12.0Compare Source
v16.12.0 (2025-11-01)
New Feature 🚀
Bug Fix 🐞
Docs 📝
28 PRs were merged
Polish 💅
Internal 🏠
3 PRs were merged
Committers: 9
graphql-hive/graphql-yoga (graphql-yoga)
v5.16.2Compare Source
Patch Changes
#4270
ba38629Thanks @ardatan! - Fixes the bug where the error masking incorrectly
sets
http.unexpectedinstead of justunexpected.{ "extensions": { - "http": { "unexpected": true - } } }v5.16.1Compare Source
Patch Changes
#4263
6f83ceaThanks @ardatan! - dependencies updates:
@whatwg-node/server@^0.10.14↗︎(from
^0.10.5, independencies)#4264
e1f52b6Thanks @renovate! - dependencies updates:
dset@^3.1.4↗︎ (fromdependencies)#4263
6f83ceaThanks @ardatan! - Update GraphiQL dependencies
jeffbski/wait-on (wait-on)
v9.0.3Compare Source
Update to jsdoc. Thanks @westonruter
Minor dependencies updated: eslint, mocha, axios
v9.0.2Compare Source
Replaced unmaintained expect-legacy package with chai. Thanks @bdkopen
wundergraph/cosmo (wgc)
v0.94.5Compare Source
Note: Version bump only for package wgc
v0.94.4Compare Source
Note: Version bump only for package wgc
v0.94.3Compare Source
Note: Version bump only for package wgc
v0.94.2Compare Source
Note: Version bump only for package wgc
v0.94.1Compare Source
Note: Version bump only for package wgc
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.