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

chore(deps): update yarn to v4.5.0 #1904

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
yarn (source) 4.0.2 -> 4.5.0 age adoption passing confidence

Release Notes

yarnpkg/berry (yarn)

v4.5.0

Compare Source

v4.4.1

Compare Source

v4.4.0

Compare Source

v4.3.1

Compare Source

v4.3.0

Compare Source

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

v4.1.1

Compare Source

v4.1.0

Compare Source

  • Tweaks -,--verbose in yarn workspaces foreach; -v will now only print the prefixes, -vv will be necessary to also print the timings.

  • Adds a new --json option to yarn run when called without script name

  • Fixes node-modules linker link: dependencies mistreatment as inner workspaces, when they point to a parent folder of a workspace

  • Fixes spurious "No candidates found" errors

  • Fixes missing executable permissions when using nodeLinker: pnpm

  • Fixes packages being incorrectly flagged as optional

  • Fixes cache key corruptions due to uncontrolled git merges

  • Fixes yarn version apply --all --dry-run making unexpected changes

  • Fixes yarn npm login when the remote registry is Verdaccio


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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label May 2, 2024
Copy link

socket-security bot commented May 2, 2024

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Protestware or potentially unwanted behavior npm/styled-components@5.3.6
  • Note: This package prints a protestware console message regarding Ukraine for users with Russian language locale
⚠︎

View full report↗︎

Next steps

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package may come along with functionality unrelated to its primary purpose.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/styled-components@5.3.6

@renovate renovate bot changed the title chore(deps): update yarn to v4.2.0 chore(deps): update yarn to v4.2.1 May 2, 2024
@renovate renovate bot force-pushed the renovate/yarn-monorepo branch 2 times, most recently from 0d02189 to fcf3f95 Compare May 8, 2024 18:58
@renovate renovate bot changed the title chore(deps): update yarn to v4.2.1 chore(deps): update yarn to v4.2.2 May 8, 2024
@renovate renovate bot changed the title chore(deps): update yarn to v4.2.2 chore(deps): update yarn to v4.3.0 Jun 10, 2024
@renovate renovate bot changed the title chore(deps): update yarn to v4.3.0 chore(deps): update yarn to v4.3.1 Jun 21, 2024
Copy link

sonarcloud bot commented Jun 21, 2024

@renovate renovate bot changed the title chore(deps): update yarn to v4.3.1 chore(deps): update yarn to v4.4.0 Aug 3, 2024
@renovate renovate bot changed the title chore(deps): update yarn to v4.4.0 chore(deps): update yarn to v4.4.1 Aug 24, 2024
@renovate renovate bot changed the title chore(deps): update yarn to v4.4.1 chore(deps): update yarn to v4.5.0 Sep 14, 2024
Copy link

sonarcloud bot commented Sep 14, 2024

Copy link

Report too large to display inline

View full report↗︎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants