release: on branch main (#2876)

This PR was opened by the [Changesets
release](https:/changesets/action) 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

- Updated dependencies
\[[`7b5b836d15247c997712a47847f603aa5887312e`](7b5b836),
[`74ca7dd617927a20d79b824851f7651ef3c40a4e`](74ca7dd),
[`3f7392b84f8b626b248b59ce81f193d0f0272045`](3f7392b)]:
    -   @apollo/[email protected]
    -   @apollo/[email protected]

## @apollo/[email protected]

### Patch Changes

- Updated dependencies
\[[`7b5b836d15247c997712a47847f603aa5887312e`](7b5b836),
[`74ca7dd617927a20d79b824851f7651ef3c40a4e`](74ca7dd),
[`ffe67dfbdb77d15dde2ab6dee66dba05c7b5c037`](ffe67df)]:
    -   @apollo/[email protected]
    -   @apollo/[email protected]
    -   @apollo/[email protected]

## @apollo/[email protected]

### Patch Changes

- Avoid `>=` comparison for `FeatureVersion` objects
([#2883](#2883))

- Fix query planning bug where `__typename` on interface object types in
named fragments can cause query plan execution to fail.
([#2886](#2886))
([#2886](#2886))

## @apollo/[email protected]

### Patch Changes

- fix: handle directive conditions on fragments when building query
graphs ([#2875](#2875))

This fix addresses issues with handling fragments when they specify
directive conditions:

- when exploding the types we were not propagating directive conditions
- when processing fragment that specifies super type of an existing type
and also specifies directive condition, we were incorrectly preserving
the unnecessary type condition. This type condition was problematic as
it could be referencing types from supergraph that were not available in
the local schema. Instead, we now drop the redundant type condition and
only preserve the directives (if specified).

- Updated dependencies
\[[`7b5b836d15247c997712a47847f603aa5887312e`](7b5b836),
[`74ca7dd617927a20d79b824851f7651ef3c40a4e`](74ca7dd)]:
    -   @apollo/[email protected]

## @apollo/[email protected]

### Patch Changes

- Add a limit to the number of options for a selection. In some cases,
we will generate a lot of possible paths to access a field. There is a
process to remove redundant paths, but when the list is too large, that
process gets very expensive. To prevent that, we introduce an optional
limit that will reject the query if too many paths are generated
([#2880](#2880))

- Updated dependencies
\[[`7b5b836d15247c997712a47847f603aa5887312e`](7b5b836),
[`74ca7dd617927a20d79b824851f7651ef3c40a4e`](74ca7dd),
[`3f7392b84f8b626b248b59ce81f193d0f0272045`](3f7392b)]:
    -   @apollo/[email protected]
    -   @apollo/[email protected]

## @apollo/[email protected]

### Patch Changes

- Updated dependencies
\[[`7b5b836d15247c997712a47847f603aa5887312e`](7b5b836),
[`74ca7dd617927a20d79b824851f7651ef3c40a4e`](74ca7dd)]:
    -   @apollo/[email protected]

## [email protected]

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>