eth-json-rpc-filters
eth-json-rpc-filters copied to clipboard
MetaMask
Bump @metamask/eth-block-tracker from 10.0.0 to 11.0.1
Bumps @metamask/eth-block-tracker from 10.0.0 to 11.0.1.
Release notes
Sourced from @metamask/eth-block-tracker's releases.
11.0.1
Changed
- Bump
@metamask/eth-json-rpc-providerfrom^4.1.0to^4.1.1(#261)- Bump
@metamask/safe-event-emitterfrom^3.0.0to^3.1.1(#261)- Bump
@metamask/utilsfrom^8.1.0to^9.1.0(#261)11.0.0
Changed
- BREAKING: Adapt to EIP-1193 provider changes by using
requestmethod of provider instead ofsendAsync(#252)
- This change included in
10.1.0was mistakenly categorised as a non-breaking change.- This requires provider object to have the
requestmethod. You need to upgrade to minimum4.1.0of@metamask/eth-json-rpc-providerso that therequestmethod is available.10.1.0
Changed
Changelog
Sourced from @metamask/eth-block-tracker's changelog.
[11.0.1]
Changed
- Bump
@metamask/eth-json-rpc-providerfrom^4.1.0to^4.1.1(#261)- Bump
@metamask/safe-event-emitterfrom^3.0.0to^3.1.1(#261)- Bump
@metamask/utilsfrom^8.1.0to^9.1.0(#261)[11.0.0]
Changed
- BREAKING: Adapt to EIP-1193 provider changes by using
requestmethod of provider instead ofsendAsync(#252)
- This change included in
10.1.0was mistakenly categorised as a non-breaking change.- This requires provider object to have the
requestmethod. You need to upgrade to minimum4.1.0of@metamask/eth-json-rpc-providerso that therequestmethod is available.[10.1.0] [DEPRECATED]
Changed
Commits
Maintainer changes
This version was pushed to npm by mcmire, a new releaser for @metamask/eth-block-tracker 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "Published by a pub.dev verified publisher"){kind=small}
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|
| npm/@metamask/[email protected] | None | 0 |
63.6 kB | mcmire |
🚮 Removed packages: npm/@metamask/[email protected]
![socket-security[bot] avatar](https://avatars.githubusercontent.com/in/156372?v=4 "Published by a pub.dev verified publisher"){kind=small}
🚨 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 | Note | Source | CI |
|---|---|---|---|---|
| Unstable ownership | npm/@metamask/[email protected] |
| 🚫 |
Next steps
What is unstable ownership?
A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.
Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.
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/[email protected] or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/@metamask/[email protected]
Looks like @metamask/eth-block-tracker is up-to-date now, so this is no longer needed.