Skip to content

Update wordpress monorepo#1891

Closed
renovate[bot] wants to merge 1 commit into
developfrom
renovate/wordpress-monorepo
Closed

Update wordpress monorepo#1891
renovate[bot] wants to merge 1 commit into
developfrom
renovate/wordpress-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 27, 2026

This PR contains the following updates:

Package Change Age Confidence
@wordpress/e2e-test-utils-playwright (source) ^1.46.0^1.47.0 age confidence
@wordpress/eslint-plugin (source) ^25.2.0^25.3.0 age confidence
@wordpress/scripts (source) ^32.2.0^32.3.0 age confidence

Release Notes

WordPress/gutenberg (@​wordpress/e2e-test-utils-playwright)

v1.47.0

Compare Source

WordPress/gutenberg (@​wordpress/eslint-plugin)

v25.3.0

Compare Source

WordPress/gutenberg (@​wordpress/scripts)

v32.3.0

Compare Source


Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 27, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: wp-stream@undefined
npm error Found: react@18.3.1
npm error node_modules/react
npm error   react@"^18.3.0" from @wordpress/babel-preset-default@8.46.0
npm error   node_modules/@wordpress/babel-preset-default
npm error   react@"^18.3.0" from @wordpress/element@6.46.0
npm error   node_modules/@wordpress/element
npm error     @wordpress/element@"^6.46.0" from @wordpress/theme@0.13.0
npm error     node_modules/@wordpress/theme
npm error       @wordpress/theme@"^0.13.0" from @wordpress/stylelint-config@23.38.0
npm error       node_modules/@wordpress/stylelint-config
npm error   2 more (@wordpress/theme, react-dom)
npm error
npm error Could not resolve dependency:
npm error dev @wordpress/scripts@"^32.3.0" from the root project
npm error
npm error Conflicting peer dependency: react@19.2.6
npm error node_modules/react
npm error   peer react@"^19.2.4" from @wordpress/scripts@32.3.0
npm error   node_modules/@wordpress/scripts
npm error     dev @wordpress/scripts@"^32.3.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-05-29T06_13_05_887Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-29T06_13_05_887Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/wordpress-monorepo branch 5 times, most recently from 6576e2f to c265db8 Compare May 29, 2026 05:52
PatelUtkarsh added a commit that referenced this pull request May 29, 2026
Adds the monorepo:wordpress preset so all @wordpress/* direct deps
(scripts, eslint-plugin, e2e-test-utils-playwright, etc.) bump in a
single PR. Combined with postUpdateOptions: [npmDedupe] this lets
Renovate produce a coherent lockfile when @wordpress/scripts requires
a newer transitive @wordpress/* on a new React major.

Motivated by PR #1891, where @wordpress/scripts@32.3.0 (React 19) was
bumped but @wordpress/babel-preset-default, @wordpress/element, and
@wordpress/theme stayed pinned on React 18 in the lockfile, causing a
persistent ERESOLVE peer-dep failure in CI.
@renovate renovate Bot force-pushed the renovate/wordpress-monorepo branch from c265db8 to 99b18e5 Compare May 29, 2026 06:13
@PatelUtkarsh
Copy link
Copy Markdown
Member

Closing in favor of a fresh Renovate run under the new config from #1895 (monorepo:wordpress grouping + npmDedupe). Renovate should recreate this with a coherent lockfile on its next cycle.

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