Skip to content

chore(deps): update yarn to v4.14.1#1673

Open
renovate[bot] wants to merge 2 commits intomainfrom
renovate/yarn-monorepo
Open

chore(deps): update yarn to v4.14.1#1673
renovate[bot] wants to merge 2 commits intomainfrom
renovate/yarn-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 24, 2026

This PR contains the following updates:

Package Change Age Confidence
yarn (source) 4.13.04.14.1 age confidence

Release Notes

yarnpkg/berry (yarn)

v4.14.1

Compare Source

v4.14.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 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.

@renovate renovate Bot added changesets-ok Override the changesets check release:dependency This PR only updates dependencies labels Apr 24, 2026
@renovate renovate Bot added this to the next-release milestone Apr 24, 2026
@renovate renovate Bot enabled auto-merge (squash) April 24, 2026 04:36
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 24, 2026

⚠️ Artifact update problem

Renovate failed to update artifacts 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: local-testing-project/yarn.lock
➤ YN0000: · Yarn 4.14.1
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error: @cedarjs/testing@file:../packages/testing/cedarjs-testing.tgz::locator=root-workspace-0b6124%40workspace%3A.: ENOENT: no such file or directory, open '/tmp/renovate/repos/github/cedarjs/cedar/packages/testing/cedarjs-testing.tgz'
➤ YN0000: └ Completed in 3s 148ms
➤ YN0000: · Failed with errors in 3s 166ms

File name: local-testing-project-live/yarn.lock
➤ YN0000: · Yarn 4.14.1
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error: @cedarjs/testing@file:../packages/testing/cedarjs-testing.tgz::locator=root-workspace-0b6124%40workspace%3A.: ENOENT: no such file or directory, open '/tmp/renovate/repos/github/cedarjs/cedar/packages/testing/cedarjs-testing.tgz'
➤ YN0000: └ Completed in 3s 439ms
➤ YN0000: · Failed with errors in 3s 459ms

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 24, 2026

Deploy Preview for cedarjs failed.

Name Link
🔨 Latest commit 55a093c
🔍 Latest deploy log https://app.netlify.com/projects/cedarjs/deploys/69f323295f41bf00084ffaea

@renovate renovate Bot force-pushed the renovate/yarn-monorepo branch from 2d45265 to 781a041 Compare April 29, 2026 12:02
@renovate renovate Bot force-pushed the renovate/yarn-monorepo branch from 781a041 to 89c8fcb Compare April 30, 2026 01:13
@nx-cloud
Copy link
Copy Markdown

nx-cloud Bot commented Apr 30, 2026

🤖 Nx Cloud AI Fix

Ensure the fix-ci command is configured to always run in your CI pipeline to get automatic fixes in future runs. For more information, please see https://nx.dev/ci/features/self-healing-ci


View your CI Pipeline Execution ↗ for commit 55a093c

Command Status Duration Result
nx run-many -t build:pack --exclude create-ceda... ✅ Succeeded 4s View ↗
nx run-many -t build ✅ Succeeded 6s View ↗
nx run-many -t test --minWorkers=1 --maxWorkers=4 ✅ Succeeded 3s View ↗
nx run-many -t test:types ✅ Succeeded 7s View ↗

☁️ Nx Cloud last updated this comment at 2026-04-30 10:00:41 UTC

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 30, 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.

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

Labels

changesets-ok Override the changesets check release:dependency This PR only updates dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant