-
-
Notifications
You must be signed in to change notification settings - Fork 13
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/post-message-stream from 7.0.0 to 8.0.0 #146
Bump @metamask/post-message-stream from 7.0.0 to 8.0.0 #146
Conversation
Bumps [@metamask/post-message-stream](https://github.com/MetaMask/post-message-stream) from 7.0.0 to 8.0.0. - [Release notes](https://github.com/MetaMask/post-message-stream/releases) - [Changelog](https://github.com/MetaMask/post-message-stream/blob/main/CHANGELOG.md) - [Commits](MetaMask/post-message-stream@v7.0.0...v8.0.0) --- updated-dependencies: - dependency-name: "@metamask/post-message-stream" dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@metamask/[email protected], npm/@metamask/[email protected] |
👍 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 |
new author ok 🙋 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dependabot merge
@@ -1724,13 +1727,20 @@ __metadata: | |||
languageName: node | |||
linkType: hard | |||
|
|||
"@noble/hashes@npm:1.3.1, @noble/hashes@npm:~1.3.0, @noble/hashes@npm:~1.3.1": | |||
"@noble/hashes@npm:1.3.1": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The older version @noble/hashes@npm:1.3.1
is still kept through pinning by ethereum-cryptography
: ethereum/js-ethereum-cryptography#104
Bumps @metamask/post-message-stream from 7.0.0 to 8.0.0.
Release notes
Sourced from
@metamask/post-message-stream
's releases.Changelog
Sourced from
@metamask/post-message-stream
's changelog.Commits
6a5629d
8.0.0 (#111)35b1d8a
Bump@metamask/auto-changelog
from 3.2.0 to 3.3.0 (#114)14228b5
Bump electron from 22.3.21 to 22.3.25 (#115)2296049
Bump@metamask/utils
from 5.0.2 to 8.1.0 (#108)210bd0d
Bump minimum Node.js version to 16 (#110)55444e1
Bump electron from 18.3.15 to 22.3.21 (#112)Maintainer changes
This version was pushed to npm by lgbot, a new releaser for
@metamask/post-message-stream
since your current version.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)