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

Version Packages (rc) #11057

Merged
merged 1 commit into from
Jul 13, 2023
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 12, 2023

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-3.8, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

release-3.8 is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on release-3.8.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@apollo/[email protected]

Minor Changes

  • #11058 89bf33c42 Thanks @phryneas! - (Batch)HttpLink: Propagate AbortErrors to the user when a user-provided signal is passed to the link. Previously, these links would swallow all AbortErrors, potentially causing queries and mutations to never resolve. As a result of this change, users are now expected to handle AbortErrors when passing in a user-provided signal.

  • #11040 125ef5b2a Thanks @phryneas! - HttpLink/BatchHttpLink: Abort the AbortController signal more granularly.
    Before this change, when HttpLink/BatchHttpLink created an AbortController
    internally, the signal would always be .aborted after the request was completed. This could cause issues with Sentry Session Replay and Next.js App Router Cache invalidations, which just replayed the fetch with the same options - including the cancelled AbortSignal.

    With this change, the AbortController will only be .abort()ed by outside events,
    not as a consequence of the request completing.

Patch Changes

  • #11053 c0ca70720 Thanks @phryneas! - Add SuspenseCache as a lazy hidden property on ApolloClient.
    This means that SuspenseCache is now an implementation details of Apollo Client
    and you no longer need to manually instantiate it and no longer need to pass it
    into ApolloProvider.
    Trying to instantiate a SuspenseCache instance in your code will now throw an
    error.

    Migration:

    -import { SuspenseCache } from '@apollo/client';
    
    -const suspenseCache = new SuspenseCache();
    
    -<ApolloProvider client={client} suspenseCache={suspenseCache} />;
    +<ApolloProvider client={client} />;

@github-actions github-actions bot changed the title Version Packages (beta) Version Packages (rc) Jul 12, 2023
@github-actions github-actions bot force-pushed the changeset-release/release-3.8 branch 3 times, most recently from 660eff7 to 6e9e889 Compare July 13, 2023 17:37
@github-actions github-actions bot force-pushed the changeset-release/release-3.8 branch from 6e9e889 to b2f3ad1 Compare July 13, 2023 17:59
@jerelmiller jerelmiller merged commit 213bde2 into release-3.8 Jul 13, 2023
@jerelmiller jerelmiller deleted the changeset-release/release-3.8 branch July 13, 2023 19:23
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant