release: on branch main

[github-actions]

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 main, this PR will be updated.

Releases

@apollo/[email protected]

Patch Changes

• Modifies the type for the argument of the @requiresScopes from [federation__Scope!]! to [[federation__Scope!]!]!. (#2738)

  The @requiresScopes directives has been pre-emptively introduced in 2.5.0 to support an upcoming Apollo Router
  feature around scoped accesses. The argument for @requiresScopes in that upcoming feature is changed to accommodate a
  new semantic. Note that this technically a breaking change to the @requiresScopes directive definition, but as the
  full feature using that directive has been released yet, this directive cannot effectively be used and this should have
  no concrete impact.

• Updated dependencies [4b9a512b, c6e0e76d, 1add932c, 6f1fddb2]:

  • @apollo/[email protected]
  • @apollo/[email protected]

@apollo/[email protected]

Patch Changes

• Fix execution error in some cases where aliases are used and some values are null. (#2716)

  The error would manifest itself as an INTERNAL_SERVER_ERROR with a message of the form Cannot read properties of null.

• Updated dependencies [4b9a512b, c6e0e76d, 1add932c, 6f1fddb2]:

  • @apollo/[email protected]
  • @apollo/[email protected]
  • @apollo/[email protected]

@apollo/[email protected]

Patch Changes

• Modifies the type for the argument of the @requiresScopes from [federation__Scope!]! to [[federation__Scope!]!]!. (#2738)

  The @requiresScopes directives has been pre-emptively introduced in 2.5.0 to support an upcoming Apollo Router
  feature around scoped accesses. The argument for @requiresScopes in that upcoming feature is changed to accommodate a
  new semantic. Note that this technically a breaking change to the @requiresScopes directive definition, but as the
  full feature using that directive has been released yet, this directive cannot effectively be used and this should have
  no concrete impact.

• Fix potential assertion error for named fragment on abstract types when the abstract type does not have the same (#2725)
  possible runtime types in all subgraphs.

  The error manifested itself during query planning with an error message of the form Cannot normalize X at Y ....

• Expands over-eager merging of field fix to handle @defer consistently (#2720)

  The previously committed #2713 fixed an issue introduced by
  #2387, ensuring that querying the same field with different
  directives applications was not merged, similar to what was/is done for fragments. But the exact behaviour slightly
  differs between fields and fragments when it comes to @defer in that for fragments, we never merge 2 similar fragments
  where both have @defer, which we do merge for fields. Or to put it more concretely, in the following query:

  query Test($skipField: Boolean!) {
    x {
      ... on X @defer {
        a
      }
      ... on X @defer {
        b
      }
    }
  }
  

  the 2 ... on X @defer are not merged, resulting in 2 deferred sections that can run in parallel. But following
  #2713, query:

  query Test($skipField: Boolean!) {
    x @defer {
      a
    }
    x @defer {
      b
    }
  }
  

  will merge both x @defer, resulting in a single deferred section.

  This fix changes that later behaviour so that the 2 x @defer are not merged and result in 2 deferred sections,
  consistently with both 1) the case of fragments and 2) the behaviour prior to
  #2387.

@apollo/[email protected]

Patch Changes

• More aggressive ignoring of indirect paths from root types when a more direct alternative exists. This optimisation (#2669)
  slightly generalize an existing heuristic of the query planner, allowing it to ignore some known inefficient options
  earlier in its process. When this optimisation can be used, this yield faster query plan computation, but by reducing
  the number of plans to be consider, this can sometimes prevent the planner to degrade it's output when it consider
  there is too many plans to consider, which can result in more optimal query plans too.
• Updated dependencies [4b9a512b, c6e0e76d, 1add932c]:
  • @apollo/[email protected]

@apollo/[email protected]

Patch Changes

• Fix potential assertion error for named fragment on abstract types when the abstract type does not have the same (#2725)
  possible runtime types in all subgraphs.

  The error manifested itself during query planning with an error message of the form Cannot normalize X at Y ....

• More aggressive ignoring of indirect paths from root types when a more direct alternative exists. This optimisation (#2669)
  slightly generalize an existing heuristic of the query planner, allowing it to ignore some known inefficient options
  earlier in its process. When this optimisation can be used, this yield faster query plan computation, but by reducing
  the number of plans to be consider, this can sometimes prevent the planner to degrade it's output when it consider
  there is too many plans to consider, which can result in more optimal query plans too.

• Updated dependencies [4b9a512b, c6e0e76d, 1add932c, 6f1fddb2]:

  • @apollo/[email protected]
  • @apollo/[email protected]

@apollo/[email protected]

Patch Changes

• Updated dependencies [4b9a512b, c6e0e76d, 1add932c]:
  • @apollo/[email protected]

[email protected]

[netlify]

✅ Deploy Preview for apollo-federation-docs canceled.

Name	Link
🔨 Latest commit	d0042c2
🔍 Latest deploy log	https://app.netlify.com/sites/apollo-federation-docs/deploys/64e672d4f7c25000071e7ecc

[codesandbox-ci]

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.