Update semver to 0.2.0 #2194
Merged
Update semver to 0.2.0 #2194
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
r? @wycats (rust_highfive has picked a reviewer for you, use r? to override) |
|
Just to double check, but there weren't any major semantic differences between 0.1 and 0.2, just API changes? |
|
One sole api addition, no changes to existing code. dtolnay/semver@f939e91...1b6550f |
bors
added a commit
that referenced
this pull request
Dec 4, 2015
I realized that Cargo wasn't using the latest semver. This doesn't include my big nom refactoring, that will be 0.3.0.
|
👍 I'm working on finishing off the nom-based one, I'll be testing cargo with it before 0.3.0. |
|
☀️ Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I realized that Cargo wasn't using the latest semver. This doesn't include my big nom refactoring, that will be 0.3.0.