Bump @metamask/connect-evm from 1.4.0 to 2.1.0#55
Conversation
Bumps [@metamask/connect-evm](https://github.com/MetaMask/connect-monorepo) from 1.4.0 to 2.1.0. - [Release notes](https://github.com/MetaMask/connect-monorepo/releases) - [Commits](https://github.com/MetaMask/connect-monorepo/compare/@metamask/connect-evm@1.4.0...@metamask/connect-evm@2.1.0) --- updated-dependencies: - dependency-name: "@metamask/connect-evm" dependency-version: 2.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 221399ef37
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@0xsequence/typescript-sdk": "workspace:*", | ||
| "@0xtrails/adapter-wagmi": "0.16.0", | ||
| "@metamask/connect-evm": "^1.4.0", | ||
| "@metamask/connect-evm": "^2.1.0", |
There was a problem hiding this comment.
Keep MetaMask within wagmi's peer range
The lockfile still resolves wagmi@3.6.16 to @wagmi/connectors@8.0.15, whose peerDependencies declare @metamask/connect-evm: ^1.3.0; setting this direct dependency to ^2.1.0 leaves the wagmi example's metaMask() connector on an unsupported peer combination. For the wagmi example, either upgrade wagmi/@wagmi/connectors to a release that declares @metamask/connect-evm@^2.1.0 support or keep the MetaMask package on 1.x.
Useful? React with 👍 / 👎.
Bumps @metamask/connect-evm from 1.4.0 to 2.1.0.
Release notes
Sourced from @metamask/connect-evm's releases.
Commits
3336743Release/38.0.0 (#330)f09a1ebRevert "Release/38.0.0 (#326)" (#329)5dfe0a5Remove stale packageManager from browser-playground (#328)0e9f4faRelease/38.0.0 (#326)827635bRevert "Release/38.0.0 (#324)" (#325)376a492chore: migrate NPM publishing to trusted publishing (OIDC) via action-npm-pub...281f668Release/38.0.0 (#324)de8796drevert: Revert moving connect-multichain into peerDep for ecosystem packages ...0ef51d3chore: normalize wallet invocation errors across transports (#312)c69a751Release/37.0.0 (#317)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@metamask/connect-evmsince 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 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)