Uh oh!
There was an error while loading. Please reload this page.
Bump next prerelease version numbers - #34674
Merged
eps1lon merged 1 commit intoOct 1, 2025
Merged
Conversation
Comparing: ae74234...38a1766 Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: (No significant changes) |
eps1lonforce-pushed
the
sebbie/10-02-bump_next_prerelease_version_numbers
branch
from
October 1, 2025 22:12
a668f27 to
2246623Compareeps1lonforce-pushed
the
sebbie/10-02-bump_next_prerelease_version_numbers
branch
from
October 1, 2025 22:17
2246623 to
38a1766Compareeps1lon
marked this pull request as ready for review
October 1, 2025 22:26
jackpope
approved these changes
Oct 1, 2025
Uh oh!
There was an error while loading. Please reload this page.
eps1lon added a commit
to eps1lon/DefinitelyTyped
that referenced
this pull request
Aug 24, 2026
The current React canary features are shipping as stable in React 19.3, so the remaining canary declarations move into the stable entrypoints. In `react`, the `<ViewTransition>` component with its `ViewTransitionProps`, `ViewTransitionInstance`, and `ViewTransitionClass` types, `addTransitionType`, the `ref` prop on `FragmentProps` together with the renderer-augmented `FragmentInstance` interface, and `submitter` on `SubmitEvent` are now stable, and the `ts5.0` fork is kept in sync. In `react-dom`, the `ViewTransitionPseudoElement` interface and the DOM-specific fields on `ViewTransitionInstance` and `FragmentInstance` move into the existing `declare module "react"` block in `index.d.ts`. `unstable_useCacheRefresh` stays in `react/canary`; both canary entrypoints remain so existing `react/canary` and `react-dom/canary` references keep resolving, with `react-dom/canary` reduced to an empty shell. Tests move from the canary test files into the stable test files, and the stale "Only passes because program includes React Canary types" comment in `formrelatedEventTests` is replaced with a real `$ExpectType` assertion. Finally, the package versions are bumped to match the React 19.3 prerelease version bump (react/react#34674): `@types/react`, `@types/react-dom`, `@types/react-is`, and `@types/react-test-renderer` to 19.3.9999, `@types/scheduler` to 0.28.9999, and `@types/use-sync-external-store` to 1.7.9999, and the `@types/react-dom` peer dependency floor on `@types/react` is raised to `^19.3.0`. Co-Authored-By: Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
eps1lon added a commit
to eps1lon/DefinitelyTyped
that referenced
this pull request
Aug 24, 2026
The current React canary features are shipping as stable in React 19.3, so the remaining canary declarations move into the stable entrypoints. In `react`, the `<ViewTransition>` component with its `ViewTransitionProps`, `ViewTransitionInstance`, and `ViewTransitionClass` types, `addTransitionType`, the `ref` prop on `FragmentProps` together with the renderer-augmented `FragmentInstance` interface, and `submitter` on `SubmitEvent` are now stable, and the `ts5.0` fork is kept in sync. In `react-dom`, the `ViewTransitionPseudoElement` interface and the DOM-specific fields on `ViewTransitionInstance` and `FragmentInstance` move into the existing `declare module "react"` block in `index.d.ts`. `unstable_useCacheRefresh` stays in `react/canary`; both canary entrypoints remain so existing `react/canary` and `react-dom/canary` references keep resolving, with `react-dom/canary` reduced to an empty shell. Tests move from the canary test files into the stable test files, and the stale "Only passes because program includes React Canary types" comment in `formrelatedEventTests` is replaced with a real `$ExpectType` assertion. Finally, the package versions are bumped to match the React 19.3 prerelease version bump (react/react#34674): `@types/react`, `@types/react-dom`, `@types/react-is`, and `@types/react-test-renderer` to 19.3.9999, `@types/scheduler` to 0.28.9999, `@types/use-sync-external-store` to 1.7.9999, `@types/react-refresh` to 0.19.9999, and `@types/use-subscription` to 1.13.9999, and the `@types/react-dom` peer dependency floor on `@types/react` is raised to `^19.3.0`. The `react-refresh` types are also brought up to date with the runtime: `findAffectedHostInstances`, removed from the runtime in react-refresh 0.15, is dropped along with its `Instance` type, and the exported `_getMountedRootCount` is added. Co-Authored-By: Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
On to the Next One