core icon indicating copy to clipboard operation
core copied to clipboard

chore(deps): bump @metamask/snaps-sdk from 1.4.0 to 3.1.1

Open dependabot[bot] opened this issue 11 months ago • 9 comments

Bumps @metamask/snaps-sdk from 1.4.0 to 3.1.1.

Release notes

Sourced from @​metamask/snaps-sdk's releases.

3.0.0

@​metamask/snaps-cli 0.38.1-flask.1

Changed

  • Update all examples to use Webpack (#1632)

@​metamask/snaps-controllers 0.38.0-flask.1

Added

  • Add onInstall and onUpdate lifecycle hooks (#1643)

Changed

  • Make updateBlockedSnaps update the registry (#1625)
  • Move source code and snap state back to controller state (#1634)

@​metamask/snaps-execution-environments 0.38.0-flask.1

Added

  • Add onInstall and onUpdate lifecycle hooks (#1643)
  • Unblock personal_sign JSON-RPC method (#1601)

@​metamask/snaps-jest 0.37.3-flask.1

Changed

  • Bump semver to ^7.5.4 (#1631)

@​metamask/snaps-types 0.38.0-flask.1

Added

  • Add onInstall and onUpdate lifecycle hooks (#1643)
    • This package now exports the OnInstallHandler and OnUpdateHandler types.

@​metamask/snaps-ui 0.37.3-flask.1

Changed

  • Bump semver to ^7.5.4 (#1631)

@​metamask/snaps-utils 0.38.0-flask.1

Added

  • Add onInstall and onUpdate lifecycle hooks (#1643)

Changed

  • Move source code and snap state back to controller state (#1634)
  • Bump semver to ^7.5.4 (#1631)

@​metamask/bip44-example-snap 0.38.0-flask.1

Changed

  • Update example to the new configuration format (#1632)

... (truncated)

Commits

Dependabot compatibility score

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)

dependabot[bot] avatar Mar 13 '24 12:03 dependabot[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 NoteSource
No contributors or author data npm/@metamask/[email protected]

View full report↗︎

Next steps

Why is contributor and author data important?

Package does not specify a list of contributors or an author in package.json.

Add a author field or contributors array to package.json.

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

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

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 rebase.

dependabot[bot] avatar Mar 15 '24 10:03 dependabot[bot]

@dependabot rebase

ccharly avatar Mar 18 '24 10:03 ccharly

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 rebase.

dependabot[bot] avatar Mar 18 '24 11:03 dependabot[bot]

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 rebase.

dependabot[bot] avatar Mar 18 '24 15:03 dependabot[bot]

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 rebase.

dependabot[bot] avatar Mar 19 '24 08:03 dependabot[bot]

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 rebase.

dependabot[bot] avatar Mar 19 '24 15:03 dependabot[bot]

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 rebase.

dependabot[bot] avatar Mar 19 '24 18:03 dependabot[bot]

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 rebase.

dependabot[bot] avatar Mar 20 '24 14:03 dependabot[bot]

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 rebase.

dependabot[bot] avatar Mar 20 '24 15:03 dependabot[bot]

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 rebase.

dependabot[bot] avatar Mar 21 '24 09:03 dependabot[bot]

Superseded by #4098.

dependabot[bot] avatar Mar 21 '24 12:03 dependabot[bot]