Skip to content
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

release: on branch main #3153

Merged
merged 1 commit into from
Sep 27, 2024
Merged

release: on branch main #3153

merged 1 commit into from
Sep 27, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 24, 2024

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

@apollo/[email protected]

Patch Changes

@apollo/[email protected]

Patch Changes

  • Fixes handling of a __typename selection during query planning process. (#3156)

    When expanding fragments we were keeping references to the same Fields regardless where those fragments appeared in our original selection set. This was generally fine as in most cases we would have same inline fragment selection sets across whole operation but was causing problems when we were applying another optimization by collapsing those expanded inline fragments creating a new selection set. As a result, if any single field selection (within that fragment) would perform optimization around the usage of __typename, ALL occurrences of that field selection would get that optimization as well.

  • Add validations for demand control directive applications (#3148)

@apollo/[email protected]

Patch Changes

@apollo/[email protected]

Patch Changes

  • Fixes handling of a __typename selection during query planning process. (#3156)

    When expanding fragments we were keeping references to the same Fields regardless where those fragments appeared in our original selection set. This was generally fine as in most cases we would have same inline fragment selection sets across whole operation but was causing problems when we were applying another optimization by collapsing those expanded inline fragments creating a new selection set. As a result, if any single field selection (within that fragment) would perform optimization around the usage of __typename, ALL occurrences of that field selection would get that optimization as well.

  • Fixes issue where contextual parameters can have naming collisions if used in multiple subgraphs (#3155)

  • Updated dependencies [2192f355f50db33fe0807d16153f357696b9f190, e1e2605b30efc488b57f62ba43436606a38a3607, 5ac01b534318105e904c1e6598070f753add3bb1]:

@apollo/[email protected]

Patch Changes

[email protected]

@github-actions github-actions bot requested a review from a team as a code owner September 24, 2024 16:57
Copy link

netlify bot commented Sep 24, 2024

Deploy Preview for apollo-federation-docs canceled.

Name Link
🔨 Latest commit df41885
🔍 Latest deploy log https://app.netlify.com/sites/apollo-federation-docs/deploys/66f5d02513ba38000867e939

Copy link

codesandbox-ci bot commented Sep 24, 2024

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.

@github-actions github-actions bot force-pushed the changeset-release/main branch 3 times, most recently from 70fe77c to 6ec3a9e Compare September 26, 2024 19:55
@sachindshinde sachindshinde merged commit ad94371 into main Sep 27, 2024
19 checks passed
@sachindshinde sachindshinde deleted the changeset-release/main branch September 27, 2024 04:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant