Fix example for usage still not published uuid 2.0.0 #6006
Merged
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
|
@bors: r+ Looks good to me, thanks! |
|
📌 Commit 45dea14 has been approved by |
bors
added a commit
that referenced
this pull request
Sep 11, 2018
Fix example for usage still not published uuid 2.0.0 IMHO There some inconsistency in https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#prepublishing-a-breaking-change We have unpublished version 2.0.0 for uuid crate in branch with same name. Now we can test it in `my-library` without waiting for publish as written in docs. But if `my-library` changes committed to its master, for `my-binary` patch need be same as in library, as uuid 2.0.0 still not published.
|
☀️ Test successful - status-appveyor, status-travis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
IMHO There some inconsistency in https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#prepublishing-a-breaking-change
We have unpublished version 2.0.0 for uuid crate in branch with same name.
Now we can test it in
my-librarywithout waiting for publish as written in docs.But if
my-librarychanges committed to its master, formy-binarypatch need be same as in library,as uuid 2.0.0 still not published.