Conversation
✅ Docs preview has no changesThe preview was not built because there were no changes. Build ID: 40cbdc521c84dbcece49430d ✅ AI Style Review — No Changes DetectedNo MDX files were changed in this pull request. Review Log: View detailed log
|
8127b2b to
4f96382
Compare
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
4f96382 to
70a7fe4
Compare
dca4a56 to
8b78236
Compare
sachindshinde
left a comment
There was a problem hiding this comment.
I was looking at next, and there's a bug/breaking change in #3391 that means we shouldn't release. I'll file a PR by tonight/early tomorrow with fixes, but I'm filing this review to block for now.
|
Filed the PR with fixes at #3422. |
8b78236 to
9fe00ac
Compare
9fe00ac to
e258889
Compare
e258889 to
573f2bb
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.
Releases
@apollo/composition@2.14.0
Minor Changes
Relax
@composeDirectivevalidation when definitions are absent in some subgraphs. (#3422)Previously, if some set of spec directives were being composed into the supergraph schema via
@composeDirective, then subgraphs with the latest version of that spec would each have to declare all of those spec directive definitions. Not following this rule would often result in composition emitting aDIRECTIVE_COMPOSITION_ERRORerror. This restriction has now been relaxed, and a definition needs to only be in at least one of those subgraphs with the latest version of that spec.As an example, the following
@composeDirectiveusage could previously fail, but is now valid.Patch Changes
the current calculated length correctly leading to inclusion of additional elements in the error/hints message.
21cf465d4c687daeed71635422718c3c7b7d2d0e,5b36fc6b5a494aa6983e0339713dc45a0bd031e3]:@apollo/gateway@2.14.0
Minor Changes
Patch Changes
the current calculated length correctly leading to inclusion of additional elements in the error/hints message.
21cf465d4c687daeed71635422718c3c7b7d2d0e,e1fd4ac10f72bb09027995f0811ec6e0021bcd49,5b36fc6b5a494aa6983e0339713dc45a0bd031e3]:@apollo/federation-internals@2.14.0
Minor Changes
Relax
@interfaceObjectvalidation for Fed 1 subgraphs. (#3392)Previously, any use of
@interfaceObjectin a Fed 2 subgraph caused anINTERFACE_OBJECT_USAGE_ERRORif any Fed 1 subgraph was present in the composition, regardless of whether the types conflicted.The check is now per-type: an error is only raised when a Fed 2 subgraph uses
@interfaceObjecton typeTand a Fed 1 subgraph has@keyon an interface also namedT.@keyon an interface in a Fed 1 subgraph does not mean it can fulfill the__typename-resolution requirement that@interfaceObjectdepends on — but they are otherwise compatible with@interfaceObjectusage on unrelated types.Patch Changes
the current calculated length correctly leading to inclusion of additional elements in the error/hints message.
@apollo/query-graphs@2.14.0
Patch Changes
21cf465d4c687daeed71635422718c3c7b7d2d0e,5b36fc6b5a494aa6983e0339713dc45a0bd031e3]:@apollo/query-planner@2.14.0
Patch Changes
21cf465d4c687daeed71635422718c3c7b7d2d0e,5b36fc6b5a494aa6983e0339713dc45a0bd031e3]:@apollo/subgraph@2.14.0
Patch Changes
21cf465d4c687daeed71635422718c3c7b7d2d0e,5b36fc6b5a494aa6983e0339713dc45a0bd031e3]:apollo-federation-integration-testsuite@2.14.0
Minor Changes
Patch Changes
the current calculated length correctly leading to inclusion of additional elements in the error/hints message.