fix: Use no-cache for fetching registry
#3760
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To prevent users from having stale registry data, we fetch using
no-cachewhich always should recheck the registry for new updates instead of relying on the browser cache. If the content has not changed the browser will re-use the existing data and we keep falling back to the previous version in state.Note
Ensure registry fetches bypass HTTP cache by calling fetch with { cache: 'no-cache' } in safeFetch.
Written by Cursor Bugbot for commit 2afb2a3. This will update automatically on new commits. Configure here.