Skip to content

Commit b0679d5

Browse files
committed
Auto merge of #6006 - EPashkin:master, r=alexcrichton
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.
2 parents c1c4fc2 + 45dea14 commit b0679d5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/doc/src/reference/specifying-dependencies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -376,7 +376,7 @@ my-library = { git = 'https://example.com/git/my-library' }
376376
uuid = "1.0"
377377

378378
[patch.crates-io]
379-
uuid = { git = 'https://github.com/rust-lang-nursery/uuid', version = '2.0.0' }
379+
uuid = { git = 'https://github.com/rust-lang-nursery/uuid', branch = '2.0.0' }
380380
```
381381

382382
Note that this will actually resolve to two versions of the `uuid` crate. The

0 commit comments

Comments
 (0)