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

v0.16.0 #189

Closed
wants to merge 6 commits into from
Closed

v0.16.0 #189

wants to merge 6 commits into from

Conversation

bergarces
Copy link
Contributor

Changed

  • BREAKING: Refactor code to split keyring from bridge logic. (#156)
  • Migrate code to TypeScript. (#174)

@bergarces bergarces requested a review from a team as a code owner June 15, 2023 10:41
@bergarces bergarces force-pushed the release/0.16.0 branch 2 times, most recently from 136c6bf to 7a44cf5 Compare June 15, 2023 10:45
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated
## [0.16.0]
### Changed
- **BREAKING:** Refactor code to split keyring from bridge logic. ([#156](https://github.com/MetaMask/eth-ledger-bridge-keyring/pull/156))
- Migrate code to TypeScript. ([#174](https://github.com/MetaMask/eth-ledger-bridge-keyring/pull/174))
Copy link
Member

Choose a reason for hiding this comment

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

This should probably be two entries: one for the added types (non-breaking), and one for the change from default export to named export (breaking).

Anything else worth noting here @mikesposito ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

CHANGELOG.md Outdated Show resolved Hide resolved
package.json Outdated
@@ -1,6 +1,6 @@
{
"name": "@metamask/eth-ledger-bridge-keyring",
"version": "0.15.0",
"version": "0.16.0",
Copy link
Member

Choose a reason for hiding this comment

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

Thoughts on making this v1 instead? @gantunesr and I are in agreement that it seems appropriate

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've bumped the version, but I cannot change the branch name.

I've created a new PR with the correct branch name and all the changes discussed: #191

@bergarces bergarces changed the title v0.16.0 v1.0.0 Jun 16, 2023
@bergarces bergarces changed the title v1.0.0 v0.16.0 Jun 16, 2023
@Gudahtt
Copy link
Member

Gudahtt commented Jun 16, 2023

Superceded by #191

@Gudahtt Gudahtt closed this Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants