Skip to content

chore(deps): update react monorepo to ^19.2.6#870

Open
renovate[bot] wants to merge 3 commits into
mainfrom
renovate/react-monorepo
Open

chore(deps): update react monorepo to ^19.2.6#870
renovate[bot] wants to merge 3 commits into
mainfrom
renovate/react-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 6, 2026

This PR contains the following updates:

Package Change Age Confidence
react (source) ^19.2.5^19.2.6 age confidence
react-dom (source) ^19.2.5^19.2.6 age confidence
react-is (source) ^19.2.5^19.2.6 age confidence

Release Notes

facebook/react (react)

v19.2.6: 19.2.6 (May 6th, 2026)

Compare Source

React Server Components


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

@renovate renovate Bot requested a review from a team as a code owner May 6, 2026 19:02
@renovate renovate Bot requested review from bjoerge and removed request for a team May 6, 2026 19:02
@renovate renovate Bot enabled auto-merge (squash) May 6, 2026 19:02
@vercel
Copy link
Copy Markdown

vercel Bot commented May 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
plugins-studio Ready Ready Preview, Comment May 18, 2026 11:51am

Request Review

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 6, 2026

⚠️ No Changeset found

Latest commit: 75af00b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 6, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​react@​19.2.61001008496100
Addednpm/​react-dom@​19.2.61001009296100
Addednpm/​react-is@​19.2.610010010096100

View full report

@renovate renovate Bot force-pushed the renovate/react-monorepo branch from ad4f17b to 2008267 Compare May 8, 2026 14:22
@renovate renovate Bot force-pushed the renovate/react-monorepo branch from 2008267 to 1c6a13c Compare May 11, 2026 08:34
@renovate renovate Bot force-pushed the renovate/react-monorepo branch from 1c6a13c to fcd27d3 Compare May 12, 2026 08:26
@renovate renovate Bot force-pushed the renovate/react-monorepo branch from fcd27d3 to 348a908 Compare May 12, 2026 08:31
@renovate renovate Bot force-pushed the renovate/react-monorepo branch from 348a908 to 8b73b6a Compare May 12, 2026 10:23
@renovate renovate Bot force-pushed the renovate/react-monorepo branch from 8b73b6a to 2ca1aab Compare May 12, 2026 16:34
@renovate renovate Bot force-pushed the renovate/react-monorepo branch from 2ca1aab to 73e266c Compare May 13, 2026 08:44
@renovate renovate Bot force-pushed the renovate/react-monorepo branch from 73e266c to a3fcee4 Compare May 15, 2026 08:32
@renovate renovate Bot force-pushed the renovate/react-monorepo branch from a3fcee4 to cbbc40a Compare May 15, 2026 08:43
@renovate renovate Bot force-pushed the renovate/react-monorepo branch from cbbc40a to 967a9ee Compare May 15, 2026 12:23
@bjoerge
Copy link
Copy Markdown
Member

bjoerge commented May 18, 2026

@copilot can you fix the lint and test errors?

auto-merge was automatically disabled May 18, 2026 10:18

Head branch was pushed to by a user without write access

Copy link
Copy Markdown
Contributor

Copilot AI commented May 18, 2026

@copilot can you fix the lint and test errors?

Fixed in 739cc66. I aligned @sanity/debug-preview-url-secret-plugin to use the workspace React catalog resolution and refreshed the lockfile, which resolves both the lint type mismatch and the React version mismatch test failure. I also verified with pnpm lint, targeted package test, full pnpm test, and non-dev workspace build.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • sanity-cdn.com
    • Triggering command: /usr/local/bin/node node /home/REDACTED/work/plugins/plugins/dev/test-studio/node_modules/.bin/../sanity/bin/sanity build sh y/do�� isable-directives in/esbuild che/node/corepack/v1/pnpm/10.32.development (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 18, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

bjoerge
bjoerge previously approved these changes May 18, 2026
@bjoerge
Copy link
Copy Markdown
Member

bjoerge commented May 18, 2026

@copilot rebase and resolve the merge conflicts in this pull request

Copy link
Copy Markdown
Contributor

Copilot AI commented May 18, 2026

@copilot rebase and resolve the merge conflicts in this pull request

Done in 75af00b. I updated the branch with latest main, resolved the pnpm-lock.yaml conflicts, and verified with pnpm lint and pnpm test.

@jordanl17
Copy link
Copy Markdown
Member

@copilot resolve the conflict in pnpm-lock using the rebase of main on this branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants