-
Notifications
You must be signed in to change notification settings - Fork 978
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
chore: prepare non-breaking releases #4537
Conversation
- core - misc/futures-bounded - misc/server - misc/webrtc-utils - protocols/kad - protocols/ping - protocols/upnp - swarm - transports/webrtc-websys - transports/webrtc
Thanks for this Max! #4530 is also included |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, sounds good to me :)
I think we might want to do a few more point releases before the breaking one but there is no need to delay these further.
Got a particular non-breaking change in mind that you would like to release before tackling https://github.com/libp2p/rust-libp2p/milestone/7 @thomaseizinger? |
Published and tagged the following crates:
|
Let me have a closer look but I just want to make sure we don't miss certain deprecations for example for the upcoming breaking features :) |
These are all ready-to-review, non-breaking changes that contain deprecations which would allow us to remove certain code sooner, i.e. with the next breaking release:
|
Description
Crates to be released:
Notes & open questions
@jxs given #4156
@mcamou given #4467 and #4466
Change checklist