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

feat!: update to [email protected] #444

Merged
merged 4 commits into from
Sep 11, 2024
Merged

Conversation

achingbrain
Copy link
Collaborator

Incorporates API changes from the upcoming [email protected] release.

BREAKING CHANGE: Can only be used with [email protected] or later

Incorporates API changes from the upcoming `[email protected]` release.

BREAKING CHANGE: Can only be used with `[email protected]` or later
@achingbrain achingbrain marked this pull request as ready for review September 11, 2024 13:06
@achingbrain achingbrain requested a review from a team as a code owner September 11, 2024 13:06
Copy link
Member

@wemeetagain wemeetagain left a comment

Choose a reason for hiding this comment

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

LGTM, theres lots of nice additions here

  • removal of libp2p 1.0 interfaces workarounds
  • alignment of CI w other libp2p packages
  • More documentation

@achingbrain achingbrain merged commit 8a5321b into master Sep 11, 2024
17 checks passed
@achingbrain achingbrain deleted the feat/update-to-libp2p-2 branch September 11, 2024 13:45
github-actions bot pushed a commit that referenced this pull request Sep 11, 2024
## [16.0.0](v15.1.2...v16.0.0) (2024-09-11)

### ⚠ BREAKING CHANGES

* Can only be used with `[email protected]` or later

### Features

* update to [email protected] ([#444](#444)) ([8a5321b](8a5321b))
@wemeetagain
Copy link
Member

🎉 This PR is included in version 16.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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 this pull request may close these issues.

2 participants