-
Notifications
You must be signed in to change notification settings - Fork 568
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/permission-controller from 7.1.0 to 8.0.0 #2142
Bump @metamask/permission-controller from 7.1.0 to 8.0.0 #2142
Conversation
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
👍 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: Next stepsTake a deeper look at the dependencyTake 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 packageIf 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 riskTo ignore an alert, reply with a comment starting with |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2142 +/- ##
=======================================
Coverage 96.78% 96.78%
=======================================
Files 324 324
Lines 7270 7270
Branches 1126 1126
=======================================
Hits 7036 7036
Misses 234 234 ☔ View full report in Codecov by Sentry. |
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
1 similar comment
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
@dependabot recreate |
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
Bumps [@metamask/permission-controller](https://github.com/MetaMask/core) from 7.1.0 to 8.0.0. - [Release notes](https://github.com/MetaMask/core/releases) - [Changelog](https://github.com/MetaMask/core/blob/main/docs/reviewing-release-prs.md) - [Commits](https://github.com/MetaMask/core/compare/@metamask/[email protected]...@metamask/[email protected]) --- updated-dependencies: - dependency-name: "@metamask/permission-controller" dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
8fb6691
to
94a0571
Compare
@SocketSecurity ignore npm/@metamask/[email protected] This package has been published. |
Bumps @metamask/permission-controller from 7.1.0 to 8.0.0.
Commits
b20eb08
Release 111.0.0 (#3821)f4b889a
chore(deps-dev): bump@metamask/create-release-branch
from 2.0.1 to 3.0.0 (#3...2c97df2
chore(user-operation-controller): Remove unnecessarypeerDependency
(#3823)7b139dc
feat: KeepPreferencesController
in sync with keyring state (#3799)007648b
Release/110.0.0 (#3810)de3dc1a
Move keyring-controller dep to devdep in Accounts Controller (#3820)ef35512
refactor: Remove duplicated code insetProviderType
(#3813)ed8423e
refactor: Remove usage of deprecatedsetProviderType
(#3807)028b711
chore(network-controller): Remove unused internal variable (#3811)72424ec
chore(deps): bump@metamask/eth-keyring-controller
from 17.0.0 to 17.0.1 (#3805)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)