core Bump @metamask/eth-snap-keyring from 2.1.1 to 3.0.0

Bumps @metamask/eth-snap-keyring from 2.1.1 to 3.0.0.

Release notes

Sourced from @metamask/eth-snap-keyring's releases.

3.0.0

Added

Add logger and now log Snap requests (#254)

Changed

BREAKING: Add KeyringExecutionContext to user ops methods (#253)

Bump @metamask/utils from 8.3.0 to 8.4.0 (#260) (#256)

Bump @metamask/keyring-api from 5.0.0 to 5.1.0 (#259)

Bump @metamask/keyring-api from 4.0.2 to 5.0.0 (#255)

2.2.2

Changed

Bump @metamask/safe-event-emitter from 3.1.0 to 3.1.1 (#251)

Bump dependencies (#246)

Bump @metamask/safe-event-emitter from 3.0.0 to 3.1.0 (#245)

Fix enforcing responses of prepareUserOperation and patchUserOperation to be synchronous (#243)

Bump @metamask/snaps-registry from 3.0.0 to 3.0.1 (#244)

2.2.1

Changed

Bump @metamask dependencies (#236)

Extract logic in 'submitRequest' (#232)

Bump @metamask/controller-utils from 8.0.3 to 8.0.4 (#233)

Bump @metamask/json-rpc-engine from 7.3.2 to 7.3.3 (#234)

Bump @metamask/approval-controller from 5.1.2 to 5.1.3 (#235)

Bump update Snap and dev dependencies (#230)

Bump @metamask/rpc-errors from 6.2.0 to 6.2.1 (#223)

Bump @metamask/snaps-utils from 6.1.0 to 7.0.0 (#224)

Bump @metamask/rpc-errors from 6.1.0 to 6.2.0 (#219)

Bump ip from 2.0.0 to 2.0.1 (#218)

Fixed

Add chainId to Keyring API requests (transaction/typed message) (#231)

Enforce async request redirect URL is in the snaps 'allowedOrigins' (#228)

2.2.0

Changed

Bump dependencies (#220)

@metamask/snaps-controllers from ^4.1.0 to ^5.0.1

@metamask/snaps-sdk from ^1.4.0 to ^2.1.0

@metamask/snaps-utils from ^5.2.0 to ^6.1.0

@metamask/utils from ^8.1.0 to ^8.3.0

@metamask/keyring-api from ^2.0.0 to ^4.0.0

2.1.2

Fixed

Fixed inconsistent signature signing (#200)

Changelog

Sourced from @metamask/eth-snap-keyring's changelog.

[3.0.0]

Added

Add logger and now log Snap requests (#254)

Changed

BREAKING: Add KeyringExecutionContext to user ops methods (#253)

Bump @metamask/utils from 8.3.0 to 8.4.0 (#260) (#256)

Bump @metamask/keyring-api from 5.0.0 to 5.1.0 (#259)

Bump @metamask/keyring-api from 4.0.2 to 5.0.0 (#255)

[2.2.2]

Changed

Bump @metamask/safe-event-emitter from 3.1.0 to 3.1.1 (#251)

Bump dependencies (#246)

Bump @metamask/safe-event-emitter from 3.0.0 to 3.1.0 (#245)

Fix enforcing responses of prepareUserOperation and patchUserOperation to be synchronous (#243)

Bump @metamask/snaps-registry from 3.0.0 to 3.0.1 (#244)

[2.2.1]

Changed

Bump @metamask dependencies (#236)

Extract logic in 'submitRequest' (#232)

Bump @metamask/controller-utils from 8.0.3 to 8.0.4 (#233)

Bump @metamask/json-rpc-engine from 7.3.2 to 7.3.3 (#234)

Bump @metamask/approval-controller from 5.1.2 to 5.1.3 (#235)

Bump update Snap and dev dependencies (#230)

Bump @metamask/rpc-errors from 6.2.0 to 6.2.1 (#223)

Bump @metamask/snaps-utils from 6.1.0 to 7.0.0 (#224)

Bump @metamask/rpc-errors from 6.1.0 to 6.2.0 (#219)

Bump ip from 2.0.0 to 2.0.1 (#218)

Fixed

Add chainId to Keyring API requests (transaction/typed message) (#231)

Enforce async request redirect URL is in the snaps 'allowedOrigins' (#228)

[2.2.0]

Changed

Bump dependencies (#220)

... (truncated)

Commits

a5266a9 3.0.0 (#261)
cb5137c chore(deps): bump @metamask/utils from 8.3.0 to 8.4.0 (#260)
0a816b6 chore(deps): bump @metamask/keyring-api from 5.0.0 to 5.1.0 (#259)
5433d91 feat!: add KeyringExecutionContext to user ops methods (#253)
c22f7be chore(deps): bump @metamask/utils from 8.3.0 to 8.4.0 (#256)
8fd9098 chore(deps): bump @metamask/keyring-api from 4.0.2 to 5.0.0 (#255)
c9faeb1 feat: add logger + now log Snap requests (#254)
bb0cde2 2.2.2 (#252)
a5aa75a chore(deps): bump @metamask/safe-event-emitter from 3.1.0 to 3.1.1 (#251)
24cb6f9 chore: bump dependencies (#246)
Additional commits viewable in compare view

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)

Mar 19 '24 12:03 dependabot[bot]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	`+480`	145 MB	metamaskbot
npm/@metamask/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	`+495`	148 MB	metamaskbot
npm/@metamask/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	`+499`	149 MB

🚮 Removed packages: npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected]

View full report↗︎

Mar 19 '24 12:03 socket-security[bot]

🚨 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
New author	npm/@metamask/[email protected]	New Author: lgbot Previous Author: gudahtt

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

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]

Mar 19 '24 12:03 socket-security[bot]