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 v3.8.6 #251

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2024

This PR contains the following updates:

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

Release Notes

yarnpkg/berry (yarn)

v3.8.6

Compare Source

v3.8.5

Compare Source

v3.8.4

Compare Source

v3.8.3

Compare Source

v3.8.2

Compare Source

v3.8.1

Compare Source

v3.8.0

Compare Source

v3.7.0

Compare Source


Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Europe/Paris, 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

sonarcloud bot commented Jan 1, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@renovate renovate bot changed the title chore(deps): update yarn to v3.7.0 chore(deps): update yarn to v3.8.0 Feb 1, 2024
@renovate renovate bot changed the title chore(deps): update yarn to v3.8.0 chore(deps): update yarn to v3.8.1 Mar 4, 2024
Copy link

sonarcloud bot commented Mar 4, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@renovate renovate bot force-pushed the renovate/yarn-monorepo branch from 30d48ec to c324eb4 Compare May 2, 2024 19:38
@renovate renovate bot changed the title chore(deps): update yarn to v3.8.1 chore(deps): update yarn to v3.8.2 May 2, 2024
Copy link

sonarcloud bot commented May 2, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@renovate renovate bot changed the title chore(deps): update yarn to v3.8.2 chore(deps): update yarn to v3.8.3 Jun 21, 2024
Copy link

sonarcloud bot commented Jun 21, 2024

@renovate renovate bot changed the title chore(deps): update yarn to v3.8.3 chore(deps): update yarn to v3.8.4 Aug 5, 2024
@renovate renovate bot changed the title chore(deps): update yarn to v3.8.4 chore(deps): update yarn to v3.8.5 Aug 24, 2024
Copy link

sonarcloud bot commented Aug 24, 2024

Copy link

socket-security bot commented Aug 24, 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
Critical CVE npm/crypto-js@3.3.0 ⚠︎
Critical CVE npm/shell-quote@1.6.1 ⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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/crypto-js@3.3.0
  • @SocketSecurity ignore npm/shell-quote@1.6.1

@renovate renovate bot changed the title chore(deps): update yarn to v3.8.5 chore(deps): update yarn to v3.8.6 Oct 18, 2024
Copy link

sonarcloud bot commented Oct 18, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants