Skip to content
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/providers from 16.0.0 to 19.0.0 #57

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jan 24, 2025

Bumps @metamask/providers from 16.0.0 to 19.0.0.

Release notes

Sourced from @​metamask/providers's releases.

19.0.0

Changed

  • BREAKING: StreamProvider no longer accepts a jsonRpcStreamName parameter (#400)
    • Previously, this parameter was used internally to create an ObjectMultiplex stream and substream for JSON-RPC communication
    • Now, the consumer is responsible for creating and managing the stream multiplexing if needed
    • The provider will use the provided stream connection directly without any multiplexing
  • BREAKING: MetaMaskInpageProvider no longer accepts a jsonRpcStreamName parameter (#400)
    • This change is inherited from StreamProvider, as MetaMaskInpageProvider extends StreamProvider
    • Stream multiplexing should be handled before provider instantiation
  • initializeInpageProvider now handles stream multiplexing internally (#400)
    • Creates an ObjectMultiplex instance and substream using the provided jsonRpcStreamName
    • This maintains backwards compatibility for consumers using initializeInpageProvider
  • createExternalExtensionProvider now handles stream multiplexing internally (#400)
    • Creates an ObjectMultiplex instance and substream for JSON-RPC communication
    • This maintains backwards compatibility for consumers using createExternalExtensionProvider

18.3.1

Changed

  • Bump @metamask/json-rpc-engine from ^10.0.1 to ^10.0.2 (#397)
  • Bump @metamask/json-rpc-middleware-stream from ^8.0.5 to ^8.0.6 (#397)
  • Bump @metamask/rpc-errors from ^7.0.1 to ^7.0.2 (#397)
  • Bump @metamask/utils from ^10.0.0 to ^11.0.1 (#397)

18.3.0

Added

  • Implement Wallet Discovery via CAIP-294 for Wallet Multichain API (#395)

18.2.0

Added

  • Add new export for initializeInpageProvider with legacy build system support (#391)
    • Previously this module could be imported from /dist/initializeInpageProvider, but this only worked with build systems that support the exports field (e.g. browserify).
    • This new initializeInpageProvider export has a JavaScript redirect for older build systems, so it should work correctly in all cases.

18.1.2

Fixed

  • Allow optional jsonRpcStreamName for initializeInpageProvider (#390)
    • This parameter was accidentally made required in v18.1.0

18.1.1

Changed

18.1.0

Added

  • Add intializeInpageProvider as package export (#380)

Fixed

  • Remove spurious typescript reference (#381)

18.0.0

... (truncated)

Changelog

Sourced from @​metamask/providers's changelog.

[19.0.0]

Changed

  • BREAKING: StreamProvider no longer accepts a jsonRpcStreamName parameter (#400)
    • Previously, this parameter was used internally to create an ObjectMultiplex stream and substream for JSON-RPC communication
    • Now, the consumer is responsible for creating and managing the stream multiplexing if needed
    • The provider will use the provided stream connection directly without any multiplexing
  • BREAKING: MetaMaskInpageProvider no longer accepts a jsonRpcStreamName parameter (#400)
    • This change is inherited from StreamProvider, as MetaMaskInpageProvider extends StreamProvider
    • Stream multiplexing should be handled before provider instantiation
  • initializeInpageProvider now handles stream multiplexing internally (#400)
    • Creates an ObjectMultiplex instance and substream using the provided jsonRpcStreamName
    • This maintains backwards compatibility for consumers using initializeInpageProvider
  • createExternalExtensionProvider now handles stream multiplexing internally (#400)
    • Creates an ObjectMultiplex instance and substream for JSON-RPC communication
    • This maintains backwards compatibility for consumers using createExternalExtensionProvider

[18.3.1]

Changed

  • Bump @metamask/json-rpc-engine from ^10.0.1 to ^10.0.2 (#397)
  • Bump @metamask/json-rpc-middleware-stream from ^8.0.5 to ^8.0.6 (#397)
  • Bump @metamask/rpc-errors from ^7.0.1 to ^7.0.2 (#397)
  • Bump @metamask/utils from ^10.0.0 to ^11.0.1 (#397)

[18.3.0]

Added

  • Implement Wallet Discovery via CAIP-294 for Wallet Multichain API (#395)

[18.2.0]

Added

  • Add new export for initializeInpageProvider with legacy build system support (#391)
    • Previously this module could be imported from /dist/initializeInpageProvider, but this only worked with build systems that support the exports field (e.g. browserify).
    • This new initializeInpageProvider export has a JavaScript redirect for older build systems, so it should work correctly in all cases.

[18.1.2]

Fixed

  • Allow optional jsonRpcStreamName for initializeInpageProvider (#390)
    • This parameter was accidentally made required in v18.1.0

[18.1.1]

... (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)

Bumps [@metamask/providers](https://github.com/MetaMask/providers) from 16.0.0 to 19.0.0.
- [Release notes](https://github.com/MetaMask/providers/releases)
- [Changelog](https://github.com/MetaMask/providers/blob/main/CHANGELOG.md)
- [Commits](MetaMask/providers@v16.0.0...v19.0.0)

---
updated-dependencies:
- dependency-name: "@metamask/providers"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 24, 2025
Copy link

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

Package New capabilities Transitives Size Publisher
npm/@metamask/[email protected] None 0 500 kB metamaskbot

View full report↗︎

Copy link
Author

dependabot bot commented on behalf of github Feb 4, 2025

Superseded by #59.

@dependabot dependabot bot closed this Feb 4, 2025
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/main/metamask/providers-19.0.0 branch February 4, 2025 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants