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

Bump @metamask/providers to ^17.1.2 #2598

Merged
merged 4 commits into from
Jul 23, 2024
Merged

Bump @metamask/providers to ^17.1.2 #2598

merged 4 commits into from
Jul 23, 2024

Conversation

Mrtenz
Copy link
Member

@Mrtenz Mrtenz commented Jul 23, 2024

This bumps @metamask/providers to ^17.1.2, which should unblock the next release.

Copy link

socket-security bot commented Jul 23, 2024

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

Package New capabilities Transitives Size Publisher
npm/@metamask/providers@17.1.2 None +6 717 kB metamaskbot
npm/rollup@3.28.1 environment, filesystem 0 2.51 MB lukastaegert
npm/vite@4.4.9 environment, eval, filesystem, network, shell, unsafe 0 3.33 MB vitebot

🚮 Removed packages: npm/@metamask/providers@17.0.0

View full report↗︎

Copy link

socket-security bot commented Jul 23, 2024

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/vite@4.4.9

View full report↗︎

Next steps

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

Copy link

codecov bot commented Jul 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.00%. Comparing base (42c73c1) to head (52f6868).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2598   +/-   ##
=======================================
  Coverage   94.00%   94.00%           
=======================================
  Files         459      459           
  Lines        9650     9650           
  Branches     1482     1482           
=======================================
  Hits         9071     9071           
  Misses        579      579           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Mrtenz Mrtenz changed the title Bump @metamask/providers to ^17.1.1 Bump @metamask/providers to ^17.1.2 Jul 23, 2024
@Mrtenz Mrtenz marked this pull request as ready for review July 23, 2024 13:16
@Mrtenz Mrtenz requested a review from a team as a code owner July 23, 2024 13:16
@Mrtenz
Copy link
Member Author

Mrtenz commented Jul 23, 2024

@SocketSecurity ignore npm/vite@4.4.9

We don't use this feature.

@Mrtenz Mrtenz merged commit 223878c into main Jul 23, 2024
156 checks passed
@Mrtenz Mrtenz deleted the mrtenz/providers@17.1.1 branch July 23, 2024 13:20
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.

2 participants