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.

Sign up for GitHub

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

Jump to bottom

recommend semver-abiding version number #1793

Closed
blaenk opened this issue Jul 9, 2015 · 4 comments
Closed

recommend semver-abiding version number #1793

blaenk opened this issue Jul 9, 2015 · 4 comments

Comments

@blaenk
Copy link
Contributor

blaenk commented Jul 9, 2015

This is a long-term feature request.

It would be great if cargo were able analyze rust code in comparison to the previous crate version to determine the severity of the changes in order to recommend --- or perhaps even enforce --- a semver-abiding version number.

I got this idea after reading that Elm does this, which I thought was pretty awesome.
@emberian
Copy link
Member

emberian commented Jul 9, 2015

There's a long series of issues on the Rust repo about doing this.

@blaenk
Copy link
Contributor Author

blaenk commented Jul 9, 2015

Alright then.

@blaenk blaenk closed this as completed Jul 9, 2015
@blaenk
Copy link
Contributor Author

blaenk commented Jul 9, 2015

I'll leave it up to you guys to close it if you decide it should be closed. It seems that this idea has been proposed before for rust in general, but I'm specifically requesting that the functionality be added to cargo when and if it's possible.

@blaenk blaenk reopened this Jul 9, 2015
@blaenk
Copy link
Contributor Author

blaenk commented Jul 9, 2015

Nevermind, I found #374

@blaenk blaenk closed this as completed Jul 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@blaenk @emberian