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

Record CHANGELOG entries for the first core release that will publish @metamask/eth-json-rpc-provider #1849

Closed
3 tasks
MajorLift opened this issue Oct 16, 2023 · 0 comments · Fixed by #1855
Closed
3 tasks
Assignees
Labels

Comments

@MajorLift
Copy link
Contributor

MajorLift commented Oct 16, 2023

  • Record any user-facing changes and dependency version updates made to @metamask/eth-json-rpc-provider during the migration process and after its last release.
    • List the migration of @metamask/eth-json-rpc-provider as an ADDED change.
  • Record any user-facing changes made to other monorepo packages during the migration process in their respective CHANGELOGs.
@MajorLift MajorLift changed the title Update CHANGELOGs in preparation for the first core release to publish . Record CHANGELOG entries for the first core release that will publish @metamask/eth-json-rpc-provider Oct 16, 2023
@MajorLift MajorLift self-assigned this Oct 16, 2023
MajorLift added a commit that referenced this issue Oct 17, 2023
## Explanation

Records CHANGELOG entries from `eth-json-rpc-provider` migration under
"Unreleased" headers for reference during the next version release.

- [x] Records updates made to the `eth-json-rpc-provider` package during
the migration process and after its last release.
- [x] Lists the migration of `@metamask/eth-json-rpc-provider` as an
ADDED change.
- [x] Records changes made to NetworkController.

## References

- Closes #1849 

## Changelog

N/A

## Checklist

- [ ] I've updated the test suite for new or updated code as appropriate
- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've highlighted breaking changes using the "BREAKING" category
above as appropriate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant