Update uuid dep to 1.x #228
Merged
+2
−2
Conversation
This file contains 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
|
Yes, this will be breaking. |
waywardmonkeys
force-pushed
the
update-uuid
branch
from
fa5ab16
to
6478782
Compare
|
uuid 0.8 is now out. |
|
The stable uuid 1.0 release is out now. |
waywardmonkeys
force-pushed
the
update-uuid
branch
from
6478782
to
2d1c125
Compare
|
@waywardmonkeys I still see the commit as bumping it to 0.7. Was there a mixup here? |
waywardmonkeys
force-pushed
the
update-uuid
branch
from
2d1c125
to
cf9f391
Compare
|
@atouchet Whoops, yes. Fixed now. |
|
This is probably a good moment to merge this because the next version will be a major version bump, necessary for a few other breaking changes (upgrading bitflags among others). |
mrobinson
approved these changes
Apr 9, 2024
|
Thanks! We'd almost made it to 6 years! |
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.
This is exposed in the public API (if the feature is enabled), I think ... so this is probably a breaking change?
This change is