Skip to content

22.0.0 #415

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.

Sign up for GitHub

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

Merged
jiexi merged 2 commits into from
Apr 17, 2025
Merged

22.0.0 #415

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
57ea596
22.0.0
invalid-email-address Apr 17, 2025
4c61c1d
update changelog
jiexi Apr 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [22.0.0]

### Changed

- **BREAKING**: `initializeProvider` announces the extensionId, when available, via a `caip-348` target on in the new `targets` property of the CAIP-294 wallet announcement event instead of the previous `extensionId` property ([#413](https://github.com/MetaMask/providers/pull/413))
Copy link
Member

@ffmcgee725 ffmcgee725 Apr 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have a link to CAIP-294 here ? Even though it's to be merged still

Copy link
Contributor

@jiexi jiexi Apr 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ehh. i vote no, not until it is finalized and merged. Alex asked the same though. I don't feel it's worth it until a more permanent link for it exists

Copy link
Member

@ffmcgee725 ffmcgee725 Apr 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's just that it would "look good" to have it here , easily accessible, and most likely we won't remember in the future to come back here and link it. And it's safe to say it WILL get merged...eventually... 💀

Don't see this as blocker though


## [21.0.0]

### Changed
Expand Down Expand Up @@ -557,7 +563,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
added deprecation warnings for them ([#30](https://github.com/MetaMask/providers/pull/30))
- Un-deprecated `sendAsync` ([#29](https://github.com/MetaMask/providers/pull/29))

[Unreleased]: https://github.com/MetaMask/providers/compare/v21.0.0...HEAD
[Unreleased]: https://github.com/MetaMask/providers/compare/v22.0.0...HEAD
[22.0.0]: https://github.com/MetaMask/providers/compare/v21.0.0...v22.0.0
[21.0.0]: https://github.com/MetaMask/providers/compare/v20.0.0...v21.0.0
[20.0.0]: https://github.com/MetaMask/providers/compare/v19.0.0...v20.0.0
[19.0.0]: https://github.com/MetaMask/providers/compare/v18.3.1...v19.0.0
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@metamask/providers",
"version": "21.0.0",
"version": "22.0.0",
"description": "A JavaScript Ethereum provider that connects to the wallet over a stream",
"keywords": [
"MetaMask",
Expand Down
Loading