update to uuid v1.0.0 (part 1 of 2) #1091
Merged
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.
The
uuid
crate has been updated to version 1.0.0 which is great and terrible. Omicron has several dependencies that all need to use the same version ofuuid
; some make that easier than others.schemars
added auuid1
feature flag (for whichuuid
will be an alias at some point) Support uuid v1 and arrayvec 0.7 GREsau/schemars#142tokio-postgres
requires us to move from thewith-uuid-0_8
feature towith-uuid-1
diesel
expanded their dependency range foruuid
so we don't need to do anything (i.e.version = ">=0.7.0, <2.0.0"
) and note that this is whatschemars
should have done Add support for uuid 1.0.0 diesel-rs/diesel#3137In addition we had to update several leaf crates we control:
uuid
as a dev-dependency) Bump schemars from 0.8.8 to 0.8.10 typify#54diesel
above)The real pain is the intertwining of
omicron
withcrucible
andpropolis
. My proposal is the following:propolis
andcrucible
PRsomicron
that refers to the revs in (2) and (3)