Skip to content

Commit

Permalink
6.4.0 (#153)
Browse files Browse the repository at this point in the history
This is the release candidate for version 6.4.0.

---------

Co-authored-by: github-actions <[email protected]>
Co-authored-by: Erik Marks <[email protected]>
  • Loading branch information
3 people authored Sep 27, 2024
1 parent b677c12 commit 1b7e953
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 2 deletions.
10 changes: 9 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [6.4.0]

### Changed

- Migrate to `ts-bridge` ([#152](https://github.com/MetaMask/rpc-errors/pull/152))
- Migrates to [ts-bridge](https://ts-bridge.dev) from `tsup`, which may resolve issues when importing this package in CommonJS or ESM.

## [6.3.1]

### Changed
Expand Down Expand Up @@ -195,7 +202,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- `serializeError`
- If the object passed to the function has a `.message` property, it will preferred over the `.message` property of the fallback error when creating the returned serialized error object

[Unreleased]: https://github.com/MetaMask/rpc-errors/compare/v6.3.1...HEAD
[Unreleased]: https://github.com/MetaMask/rpc-errors/compare/v6.4.0...HEAD
[6.4.0]: https://github.com/MetaMask/rpc-errors/compare/v6.3.1...v6.4.0
[6.3.1]: https://github.com/MetaMask/rpc-errors/compare/v6.3.0...v6.3.1
[6.3.0]: https://github.com/MetaMask/rpc-errors/compare/v6.2.1...v6.3.0
[6.2.1]: https://github.com/MetaMask/rpc-errors/compare/v6.2.0...v6.2.1
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@metamask/rpc-errors",
"version": "6.3.1",
"version": "6.4.0",
"description": "Ethereum RPC and Provider errors",
"keywords": [
"rpc",
Expand Down

0 comments on commit 1b7e953

Please sign in to comment.