chore(deps): update yarn to v3.8.1

renovate[bot] commented 6 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
yarn (source)	`3.8.0` -> `3.8.1`

Release Notes

yarnpkg/berry (yarn)

### [`v3.8.1`](https://togithub.com/yarnpkg/berry/compare/a71d42c2ffd6278a202cccb5fb92c3ac0caf9cae...4308dca8091438e8f88682e59ef5ba5bc72241ca) [Compare Source](https://togithub.com/yarnpkg/berry/compare/a71d42c2ffd6278a202cccb5fb92c3ac0caf9cae...4308dca8091438e8f88682e59ef5ba5bc72241ca)

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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 has been generated by Mend Renovate. View repository job log here.

vercel[bot] commented 6 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
react-hackernews	✅ Ready (Inspect)	Visit Preview	Mar 11, 2024 0:24am

renovate[bot] commented 6 months ago

⚠ 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: yarn.lock

Internal Error: Error when performing the request to https://registry.npmjs.org/yarn; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at fetch (/opt/containerbase/tools/corepack/0.26.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22878:11)
    at async fetchAsJson (/opt/containerbase/tools/corepack/0.26.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22892:20)
    at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.26.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22942:20)
    at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.26.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22975:14)
    at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.26.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23537:25)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.26.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23644:30)
    at async BinaryCommand.validateAndExecute (/opt/containerbase/tools/corepack/0.26.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21164:22)
    at async _Cli.run (/opt/containerbase/tools/corepack/0.26.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22139:18)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.26.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:24371:12)

changeset-bot[bot] commented 6 months ago

⚠️ No Changeset found

Latest commit: 1bd8ac886a2b4a2b6ca635c83208752c1f2d6307

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.

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

JounQin / react-hackernews