-
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
*: Consider using semverver #2635
Comments
Our current version bump results in a build failure see #2647 (comment) |
Instead of |
Thanks for reviving this @mxinden - I had lost track of it because of work, I agree, particularly because semverver is tightly coupled to specific nightly compiler versions and takes work to stay in sync. I will give it a try on the PR. |
With #2647 I am closing here. |
Description
Consider using https://github.com/rust-lang/rust-semverver to enforce semantic versioning. Instructions on how to integrate semverver in CI can be found on https://github.com/rust-lang/rust-semverver#ci-setup.
Motivation
Complying with Semver makes it easier for users to consume rust-libp2p. Having an automated compliance check makes maintaining rust-libp2p easier.
Are you planning to do it yourself in a pull request?
Help wanted!
The text was updated successfully, but these errors were encountered: