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
Remove all deprecated items #3647
Comments
I will take a go at this. I would suggest creating different PRs for each individual sub crate. This way we can merge the removal along with other breaking changes. Although this is kind of boring work, I'm happy to be back :) Tracking:
|
This patch removes the 3 out of 4 deprecated public modules. I've left `store` for now because we made some mistakes in declaring that. The items within `store` still need to be publicly visible but I haven't yet figured out a good way of exporting / naming them. Thus, I've left that to a follow-up PR. Related: #3647. Pull-Request: #3896.
Hey guys !! Any estimate about when the 0.52.0 version will be released ? We are eagerly waiting to see it coming since the project on which I am working has some dependency mismatch with matrix-sdk and the only way we can get through this normally is to wait till libp2p 0.52.0 is released. |
We are aiming to release within the next week, latest early June. |
Deprecated in libp2p#3738 Deprecation released with `v0.51.3`. Follow up to libp2p#3896 Part of libp2p#3647
@thomaseizinger, I assume that we don't need to hold the upcoming release for any remaining deprecation-removals. Please correct me if I'm wrong. |
Nope, no need! I think apart from the |
Description
Remove all
#[deprecated]
items from the codebase.Doing so is a breaking change, meaning we only want to do this once we cut the next breaking release.
Motivation
Keeping things lean and lower complexity.
Are you planning to do it yourself in a pull request?
Maybe.
The text was updated successfully, but these errors were encountered: