Skip to content
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

deps: yarn 1.22.21 #19

Merged
merged 1 commit into from
Feb 25, 2024
Merged

deps: yarn 1.22.21 #19

merged 1 commit into from
Feb 25, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 22, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
yarn 1.22.19 -> 1.22.21 age adoption passing confidence

Release Notes

yarnpkg/yarn (yarn)

v1.22.21

Compare Source

[!WARNING]
This release is missing a couple of artifacts (the .msi/.rpm/.deb/.asc files); we're working on fixing this.

  • Fixes an issue in the v1.22.20 when calling Yarn from a project subfolder, outside of a Corepack context.

  • Added a SKIP_YARN_COREPACK_CHECK environment variable to skip the Corepack check.

v1.22.20

Compare Source

  • Important: Punycode is now embed within the bundle, as it has been deprecated by Node.js and will be removed in a future version.

  • A message will be displayed when Yarn 1.22 notices that the local project has a package.json file referencing a non-1.x Yarn release via the packageManager field. The message will explain that the project is intended to be used with Corepack.

  • The yarn-error.log files won't be generated anymore, as we don't process non-critical 1.x bug reports (we however process all bugs reported on https://github.com/yarnpkg/berry; we just released the 4.0.2 release there).

  • The yarn set version x.y.z command will now install the exact x.y.z version (prior to this change it used to first install the latest version, and only in a second step would it downgrade to x.y.z; this was causing issues when we bump the minimal Node.js version we support, as running yarn set version 3.6.4 wouldn't work on Node 16).

  • Prevents crashes when reading from an empty .yarnrc.yml file.


Configuration

📅 Schedule: Branch creation - "after 3:00 am and before 6:00 am on Monday and Friday" in timezone Australia/Melbourne, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot requested a review from a team as a code owner February 22, 2024 16:47
Copy link

changeset-bot bot commented Feb 22, 2024

⚠️ No Changeset found

Latest commit: c1450a1

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

@askoufis askoufis enabled auto-merge (squash) February 25, 2024 23:17
@renovate renovate bot force-pushed the renovate-yarn-1.x branch from c3d2b48 to c1450a1 Compare February 25, 2024 23:17
@askoufis askoufis merged commit bad9a43 into master Feb 25, 2024
3 checks passed
@askoufis askoufis deleted the renovate-yarn-1.x branch February 25, 2024 23:18
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