Repository navigation
Invalidate retained PR data after visibility loss - #354
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Code coverage overviewLanguages: TypeScript TypeScript / code-coverage-agent
View coverage of the 10 most impacted files.
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
BunsDev
marked this pull request as ready for review
October 21, 2026 00:31
This was referenced Oct 21, 2026
2 of 10 tasks
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After a successful PR read, a 403/404 followed by a network failure could expose old cached content. This repair invalidates affected PR views, inbox entries, and shared file slices, and prevents overlapping searches, transport responses, and account confirmation from restoring denied data. Accessible inbox repositories remain available as explicitly incomplete results.
Stacked on #349. Includes regressions for denied data resurrection, sibling context slices, post-confirmation races, and mixed accessible/denied inbox results.
Validation on
4dd5bb59afd7d55f5c05d5580c7a1d8bb4648698:pnpm build,pnpm typecheck, andpnpm testpassed: 1,938 passed, 16 skipped.Authenticated renderer navigation and full UI E2E remain part of #346 integration; this service repair does not claim that acceptance.