-
Notifications
You must be signed in to change notification settings - Fork 1k
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: deprecate webrtc
and quic
features in libp2p
crate
#3580
Conversation
tls
, webrtc
and quic
features from libp2p
cratewebrtc
and quic
features from libp2p
crate
9a76666
to
830528b
Compare
@mxinden I now changed this to deprecate instead of remove the modules which allows us to release this as non-breaking change. Hopefully, this contributes to lessen the problems we have with these alphas. |
webrtc
and quic
features from libp2p
cratewebrtc
and quic
features in libp2p
crate
This pull request has merge conflicts. Could you please resolve them @thomaseizinger? 🙏 |
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.
I am in favor of this, minus the small comment below.
Co-authored-by: Max Inden <mail@max-inden.de>
I am removing the dependency on #3615. Based on #3386 (comment), I am assuming that @mxinden is in favor of the new changelog syntax so I am using this here and we can iterate on the exact wording in #3615 after that. |
This pull request has merge conflicts. Could you please resolve them @thomaseizinger? 🙏 |
… module of libp2p. See: libp2p#3580.
Description
We currently expose
libp2p-quic
andlibp2p-webrtc
as submodules from thelibp2p
crate despite those only being "alpha" status. This causes problems because we need to pin those dependencies due tocargo
automatically upgrading alphas (which are allowed to incur breaking changes as per semver spec). Additionally, exposing these modules practically hides the "alpha" state of those modules, rendering it kind of obsolete.The "alpha" state is still true for those modules, thus to properly communicate this to users, we deprecate the modules and require users to spell out the dependency and the alpha version in their manifest.
Notes & open questions
This is a breaking change and thus a draft for now. We could also deprecate them first and thus release this instantly. What do you think @mxinden ?Change checklist