chore: react@next CI checks - #46
Merged
Merged
Conversation
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.
Summary
Adds a release guard that fails once npm
react@latestmoves past the supported stable window defined intestRenderer.supportedReactRange, and updates automation to exercise that policy in nightly CI. It also adds the event-related host config hooks newerreact-reconcilerbuilds expect at runtime, updates ESLint handling for.mjsscripts, renames formatting scripts toformat/format:fix, and covers the release guard with a dedicated Jest test.Type of change
Other: CI and release guard maintenance for React compatibility support.
How Has This Been Tested?
bun run typecheckbun x jest --watchman=falsebun run formatChecklist:
Additional Notes:
peerDependencies.reactremains broad as^19.0.0, whiletestRenderer.supportedReactRangeexplicitly records the tested stable support window as>=19.0.0 <19.3.0.format/format:fixwhile still using Prettier under the hood.19.0.0and~19.0.0, while nightly adds the React release guard and still keeps a dedicated React canary job.testRenderer.supportedReactRange, checks npm metadata, and fails with an actionable message once the latest stable React release moves outside that configured window.eslint.config.jsnow disables typed lint rules forjs/mjs/cjsfiles so the new release-guard script can live outside the TypeScript project graph.actions/checkout@v5andcodecov-action@v5, and the workflows setFORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true.trackSchedulerEvent,resolveEventType, andresolveEventTimeStampso newer reconciler builds do not crash on missing runtime hooks even when@types/react-reconcilerlags behind.