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

Update babel monorepo to v7.24.7 #961

Merged
merged 1 commit into from
Jul 9, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/cli (source) 7.24.6 -> 7.24.7 age adoption passing confidence
@babel/core (source) 7.24.6 -> 7.24.7 age adoption passing confidence
@babel/eslint-parser (source) 7.24.6 -> 7.24.7 age adoption passing confidence
@babel/preset-env (source) 7.24.6 -> 7.24.7 age adoption passing confidence

Release Notes

babel/babel (@​babel/cli)

v7.24.7

Compare Source

🐛 Bug Fix
🏠 Internal
  • babel-helpers, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime

Configuration

📅 Schedule: 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 these updates 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.

Copy link

socket-security bot commented Jun 5, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@typescript-eslint/eslint-plugin@6.21.0 Transitive: environment, filesystem +16 5.02 MB jameshenry
npm/@typescript-eslint/parser@6.21.0 Transitive: environment, filesystem +12 1.96 MB jameshenry

🚮 Removed packages: npm/@babel/cli@7.24.6, npm/@babel/core@7.24.6, npm/@babel/eslint-parser@7.24.6, npm/@babel/preset-env@7.24.6

View full report↗︎

Copy link

socket-security bot commented Jun 5, 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
Filesystem access npm/glob@7.2.3
  • orphan: npm/glob@7.2.3
🚫
Filesystem access npm/globby@11.1.0 🚫
Environment variable access npm/bs-logger@0.2.6
  • orphan: npm/bs-logger@0.2.6
🚫
Filesystem access npm/bs-logger@0.2.6
  • orphan: npm/bs-logger@0.2.6
🚫
Environment variable access npm/bs-logger@0.2.6
  • orphan: npm/bs-logger@0.2.6
🚫
Environment variable access npm/minimatch@9.0.3 🚫
Environment variable access npm/minimatch@9.0.3 🚫
Critical CVE npm/@babel/traverse@7.22.5
  • orphan: npm/@babel/traverse@7.22.5
🚫
Filesystem access npm/fast-glob@3.3.2 🚫

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

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/glob@7.2.3
  • @SocketSecurity ignore npm/globby@11.1.0
  • @SocketSecurity ignore npm/bs-logger@0.2.6
  • @SocketSecurity ignore npm/minimatch@9.0.3
  • @SocketSecurity ignore npm/@babel/traverse@7.22.5
  • @SocketSecurity ignore npm/fast-glob@3.3.2

@renovate renovate bot force-pushed the renovate/babel-monorepo branch 5 times, most recently from 724c489 to 422a238 Compare June 22, 2024 13:15
@renovate renovate bot force-pushed the renovate/babel-monorepo branch from 422a238 to 9134325 Compare June 26, 2024 01:57
@renovate renovate bot force-pushed the renovate/babel-monorepo branch from 9134325 to 71a93e1 Compare July 9, 2024 19:38
@renovate renovate bot merged commit 50b3761 into master Jul 9, 2024
6 checks passed
@renovate renovate bot deleted the renovate/babel-monorepo branch July 9, 2024 21:25
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.

0 participants