Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork10.8k
Initial-load fetchers should not automatically revalidate on GET navigations#10688
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
changeset-botbot commentedJul 11, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
🦋 Changeset detectedLatest commit:a666ed2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means?Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Follow up to#10623 which inadvertently started revalidating initial-load fetchers on GET navigations, when it should only revalidate (without calling
shouldRevalidate) on explicit revalidations (submissions,useRevalidate, etc.).Discord thread in which this was raised:https://discord.com/channels/770287896669978684/1128075241579614208/1128080680417501215