Skip to content

chore(deps): bump react and @types/react - #361

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/multi-7f19880bf6
Closed

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/multi-7f19880bf6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 15, 2026

Copy link
Copy Markdown
Contributor

Bumps react and @types/react. These dependencies needed to be updated together.
Updates react from 19.2.8 to 19.3.0

Release notes

Sourced from react's releases.

19.3.0 (September 9, 2026)

Below is a list of all new features, APIs, and bug fixes.

Read the React 19.3 release post for more information.

New React Features

New React DOM Features

  • browser(): a new react-dom API that returns a usable which errors during server rendering and resolves in the browser. use(browser()) inside a <Suspense> boundary marks a subtree as browser-only without reporting a recoverable error (@​gnoff: #37143, #37241)
    • Added an onBrowserBailout option to the react-dom/server APIs to observe when a subtree defers to the browser (@​gnoff #37193)

Notable changes

All Changes

React

... (truncated)

Changelog

Sourced from react's changelog.

19.3.0 (September 9, 2026)

New React Features

New React DOM Features

  • browser(): a new react-dom API that returns a usable which errors during server rendering and resolves in the browser. use(browser()) inside a <Suspense> boundary marks a subtree as browser-only without reporting a recoverable error (@​gnoff: #37143, #37241)
    • Added an onBrowserBailout option to the react-dom/server APIs to observe when a subtree defers to the browser (@​gnoff #37193)

Notable changes

All Changes

React

... (truncated)

Commits

Updates @types/react from 19.2.18 to 19.3.0

Commits

@dependabot @github

dependabot Bot commented on behalf of github Sep 15, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, triage. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot
dependabot Bot requested a review from lamemustafa as a code owner September 15, 2026 00:26
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.

Bumps [react](https://github.com/react/react/tree/HEAD/packages/react) and [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react). These dependencies needed to be updated together.

Updates `react` from 19.2.8 to 19.3.0
- [Release notes](https://github.com/react/react/releases)
- [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react/react/commits/v19.3.0/packages/react)

Updates `@types/react` from 19.2.18 to 19.3.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

---
updated-dependencies:
- dependency-name: "@types/react"
  dependency-version: 19.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
- dependency-name: react
  dependency-version: 19.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@lamemustafa

Copy link
Copy Markdown
Owner

Closing in favour of #362, which fixes the cause rather than this instance.

This PR is not merely unlucky — it is what .github/dependabot.yml is currently guaranteed to produce on every React release. The config deliberately leaves the runtime dependencies ungrouped so each arrives as its own reviewable PR, which is right for @wxt-dev/module-react but cannot work for react and react-dom: React enforces exact-version equality between them and refuses to run otherwise.

Error: Incompatible React versions: The "react" and "react-dom" packages must have the exact same version.

That is the failure in Verify extension here — 25 suites, all of the panel and popup component tests, from react 19.3.0 resolving against react-dom 19.2.8. Merging a hand-patched lockfile onto this branch would have produced a green PR and left the config free to do the same thing next release.

#362 groups the four React packages into their own react group — still separate from dev-tooling, still its own runtime PR with its own disposition — and adds tests/repo/react-runtime-version-parity.test.ts, which fails whenever the resolved react and react-dom versions in pnpm-lock.yaml diverge, however they came apart. That guard was confirmed to fail against this exact mismatch before being kept.

The React 19.3.0 upgrade is not lost: Dependabot will reopen it as a single grouped PR carrying react-dom with it once #362 lands.

@dependabot @github

dependabot Bot commented on behalf of github Sep 15, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/multi-7f19880bf6 branch September 15, 2026 13:31
lamemustafa added a commit that referenced this pull request Sep 15, 2026
…one (#362)

`.github/dependabot.yml` deliberately left the runtime dependencies ungrouped so
each arrives as its own reviewable PR. React makes that impossible for two of
them: it refuses to run when `react` and `react-dom` disagree -- "Incompatible
React versions: the react and react-dom packages must have the exact same
version". Separate PRs therefore do not produce two independently reviewable
updates; they produce one broken PR and one that cannot merge before it. #361
bumped react 19.2.8 without react-dom and failed 25 suites for exactly that
reason, and this recurs on every React release.

Grouping the two preserves what the ungrouped rule was actually for: this is
still a runtime PR of its own, separate from dev-tooling, reviewed and
dispositioned on its own. `@wxt-dev/module-react` stays ungrouped; it carries no
such constraint.

Adds `tests/repo/react-runtime-version-parity.test.ts` so the grouping does not
rely on being remembered, following `node-runtime-types-alignment.test.ts`: one
assertion against the resolved versions in `pnpm-lock.yaml`, which state what is
installed and cannot be written as a range or commented out. Confirmed to fail
when the lockfile is edited to the exact #361 mismatch.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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.

1 participant