fix(deps): update react to ^19.3.0 - #3260
Open
renovate[bot] wants to merge 2 commits into
Open
renovate[bot] wants to merge 2 commits into
renovate[bot] wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: ffcc0e9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 14 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
christianhg
added a commit
that referenced
this pull request
Sep 10, 2026
`react` and `react-dom` are on `minimumReleaseAgeExclude`, but `react-dom` depends on `scheduler`, which ships from the React monorepo in the same release. When Renovate bumped the react catalog entries to ^19.3.0 (#3260), pnpm's lockfile update failed with `ERR_PNPM_NO_MATURE_MATCHING_VERSION`: `react-dom@19.3.0` requires `scheduler@^0.28.0`, whose only satisfying version was published the same day, inside the 3-day age window. Renovate then opened the PR with manifest edits but no lockfile, and every CI job failed at `pnpm install --frozen-lockfile`. Excluding `scheduler` lets a react bump resolve immediately, matching the trust already extended to `react`, `react-dom`, and `react-is`. Verified by regenerating the lockfile with the react catalog entries at ^19.3.0: fails with the mature-version error without the exclusion, resolves with it. Resolution of the current lockfile is unchanged.
renovate
Bot
force-pushed
the
renovate/react
branch
from
September 10, 2026 07:05
4b501e8 to
4308de4
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
Bundle Stats✅ No significant changes. All scenario measurements (7)🗺️
Significant means at least 1.0 KB and 1% gzip, or at least 5 ms and 10% import time. |
renovate
Bot
force-pushed
the
renovate/react
branch
from
September 10, 2026 23:44
3c47b63 to
2fc6d15
Compare
renovate
Bot
force-pushed
the
renovate/react
branch
from
September 15, 2026 12:00
e02fdf6 to
ac1efa7
Compare
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.
This PR contains the following updates:
^19.2.8→^19.3.0^19.2.8→^19.3.0Release Notes
react/react (react)
v19.3.0Compare Source
react/react (react-dom)
v19.3.0Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate using a curated preset maintained by