Skip to content

Handle upstream fetch failures gracefully - #423

Open
ya-nsh wants to merge 1 commit into
react-native-community:masterfrom
ya-nsh:feat/upstream-fetch-resilience
Open

Handle upstream fetch failures gracefully#423
ya-nsh wants to merge 1 commit into
react-native-community:masterfrom
ya-nsh:feat/upstream-fetch-resilience

Conversation

@ya-nsh

@ya-nsh ya-nsh commented Jun 3, 2026

Copy link
Copy Markdown

Summary

  • guard upstream RELEASES and diff fetches with response.ok handling
  • validate release payloads before version-selector semver work so bad upstream bodies do not blank-screen the app
  • show user-facing retryable error alerts for release-list and diff-load failures, including a copyable upstream URL for debugging
  • add focused unit coverage for release-payload sanitization and HTTP/error-state formatting

Fixes #420.

Verification

  • corepack yarn lint
  • corepack yarn typecheck
  • corepack yarn test --runInBand
  • corepack yarn build (build completes successfully; CRA/fork-ts-checker prints the existing Node 22 Cannot set property mark warning before reporting Compiled successfully)

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.

Gracefully handle upstream fetch failures for release lists and diffs

1 participant