Skip to content

Update dependency @10up/block-components to v1.21.2 #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 24, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@10up/block-components (source) 1.20.0 -> 1.21.2 age adoption passing confidence

Release Notes

10up/block-components (@​10up/block-components)

v1.21.2: 1.21.2

Compare Source

What's Changed

New Contributors

Full Changelog: 10up/block-components@v1.21.1...v1.21.2

v1.21.1: 1.21.1

Compare Source

What's Changed

Full Changelog: 10up/block-components@v1.21.0...v1.21.1

v1.21.0

Compare Source

What's Changed

New Contributors

Full Changelog: 10up/block-components@v1.20.5...v1.21.0

v1.20.5

Compare Source

Full Changelog: 10up/block-components@v1.20.4...v1.20.5

v1.20.4: 1.20.4

Compare Source

  • Set peer dependency version of react & react-doc to 18.3 to match the version in WordPress Core. This is to prevent an issue where sometimes it mixed react 18 with 19 which caused odd issues in some instances

Full Changelog: 10up/block-components@v1.20.3...v1.20.4

v1.20.3

Compare Source

v1.20.2

Compare Source

v1.20.1: 1.20.1

Compare Source

What's Changed

New Contributors

Full Changelog: 10up/block-components@v1.20.0...v1.20.1


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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 this update again.


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

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

Copy link
Contributor Author

renovate bot commented May 24, 2025

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @10up/[email protected]
npm ERR! node_modules/@10up/eslint-config
npm ERR!   peer @10up/eslint-config@"^3.0.0" from [email protected]
npm ERR!   node_modules/10up-toolkit
npm ERR!     dev 10up-toolkit@"^6.0.0" from the root project
npm ERR!   @10up/eslint-config@"^4.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! @10up/eslint-config@"^4.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint-config-prettier
npm ERR!   peer eslint-config-prettier@"^9.1.0" from @10up/[email protected]
npm ERR!   node_modules/@10up/eslint-config
npm ERR!     @10up/eslint-config@"^4.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-07-05T15_52_38_593Z-debug-0.log

@renovate renovate bot force-pushed the renovate/10up-block-components-1.x-lockfile branch 2 times, most recently from 9fa0edf to ff700dd Compare June 2, 2025 11:02
@renovate renovate bot changed the title Update dependency @10up/block-components to v1.20.4 Update dependency @10up/block-components to v1.20.5 Jun 2, 2025
@renovate renovate bot force-pushed the renovate/10up-block-components-1.x-lockfile branch from ff700dd to bc1558f Compare June 3, 2025 20:45
@renovate renovate bot changed the title Update dependency @10up/block-components to v1.20.5 Update dependency @10up/block-components to v1.21.0 Jun 3, 2025
@renovate renovate bot force-pushed the renovate/10up-block-components-1.x-lockfile branch from bc1558f to c5a0a69 Compare June 16, 2025 16:44
@renovate renovate bot changed the title Update dependency @10up/block-components to v1.21.0 Update dependency @10up/block-components to v1.21.1 Jun 16, 2025
@renovate renovate bot force-pushed the renovate/10up-block-components-1.x-lockfile branch from c5a0a69 to 775c00d Compare June 18, 2025 07:03
@renovate renovate bot changed the title Update dependency @10up/block-components to v1.21.1 Update dependency @10up/block-components to v1.21.2 Jun 18, 2025
@renovate renovate bot force-pushed the renovate/10up-block-components-1.x-lockfile branch from 775c00d to 0b8610c Compare June 22, 2025 13:46
@renovate renovate bot force-pushed the renovate/10up-block-components-1.x-lockfile branch from 0b8610c to 2b606ce Compare July 5, 2025 15:52
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.

0 participants