Skip to content

Update Rust crate uuid to v1.23.0#29

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/uuid-1.x-lockfile
Open

Update Rust crate uuid to v1.23.0#29
renovate[bot] wants to merge 1 commit intomainfrom
renovate/uuid-1.x-lockfile

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Jan 10, 2025

This PR contains the following updates:

Package Type Update Change
uuid dependencies minor 1.6.11.23.0

Release Notes

uuid-rs/uuid (uuid)

v1.23.0

Compare Source

What's Changed

New Contributors

Special thanks

@​meng-xu-cs raised a series of bugs against the timestamp logic in uuid using automated tooling. The issues themselves were reasonably and responsibly presented and the end result is a better uuid library for everyone. Thanks!

Deprecations

This release includes the following deprecations:

  • Context: Renamed to ContextV1
  • Timestamp::from_gregorian: Renamed to Timestamp::from_gregorian_time

Change to Version::Max

Version::Max's u8 representation has changed from 0xff to 0x0f to match the value returned by Uuid::get_version_num.

Change to Uuid::get_version for the max UUID

Uuid::get_version will only return Some(Version::Max) if the UUID is actually the max UUID (all bytes are 0xff). Previously it would return Some if only the version field was 0x0f. This change matches the behaviour of the nil UUID, which only returns Some(Version::Nil) if the UUID is the nil UUID (all bytes are 0x00).

Full Changelog: uuid-rs/uuid@v1.22.0...v1.23.0

v1.22.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.21.0...v1.22.0

v1.21.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.20.0...v1.21.0

v1.20.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.19.0...v1.20.0

v1.19.0

Compare Source

What's Changed

Full Changelog: uuid-rs/uuid@v1.18.1...v1.19.0

v1.18.1

Compare Source

What's Changed

Full Changelog: uuid-rs/uuid@v1.18.0...v1.18.1

v1.18.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.17.0...v1.18.0

v1.17.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.16.0...v1.17.0

v1.16.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.15.1...v1.16.0

v1.15.1

Compare Source

What's Changed

Full Changelog: uuid-rs/uuid@v1.15.0...v1.15.1

v1.15.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.14.0...v1.15.0

v1.14.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.13.2...v1.14.0

v1.13.2

Compare Source

What's Changed

Full Changelog: uuid-rs/uuid@1.13.1...v1.13.2

v1.13.1

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@1.13.0...1.13.1

v1.13.0

Compare Source

⚠️ Potential Breakage

This release updates our version of getrandom to 0.3 and rand to 0.9. It is a potentially breaking change for the following users:

no-std users who enable the rng feature

uuid still uses getrandom by default on these platforms. Upgrade your version of getrandom and follow its new docs on configuring a custom backend.

wasm32-unknown-unknown users who enable the rng feature without the js feature

Upgrade your version of getrandom and follow its new docs on configuring a backend.

You'll also need to enable the rng-getrandom or rng-rand feature of uuid to force it to use getrandom as its backend:

[dependencies.uuid]
version = "1.13.0"
- features = ["v4"]
+ features = ["v4", "rng-getrandom"]

[dependencies.getrandom]
version = "0.3"

If you're on wasm32-unknown-unknown and using the js feature of uuid you shouldn't see any breakage. We've kept this behavior by vendoring in getrandom's web-based backend when the js feature is enabled.

What's Changed

Full Changelog: uuid-rs/uuid@1.12.1...1.13.0

v1.12.1

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@1.12.0...1.12.1

v1.12.0

Compare Source

⚠️ Possible Breakage

This release includes additional PartialEq implementations on Uuid, which can break inference in some cases.

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@1.11.1...1.12.0

v1.11.1

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@1.11.0...1.11.1

v1.11.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@1.10.0...1.11.0

v1.10.0

Compare Source

Deprecations

This release deprecates and renames the following functions:

  • Builder::from_rfc4122_timestamp -> Builder::from_gregorian_timestamp
  • Builder::from_sorted_rfc4122_timestamp -> Builder::from_sorted_gregorian_timestamp
  • Timestamp::from_rfc4122 -> Timestamp::from_gregorian
  • Timestamp::to_rfc4122 -> Timestamp::to_gregorian

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@1.9.1...1.10.0

v1.9.1

Compare Source

What's Changed

Full Changelog: uuid-rs/uuid@1.9.0...1.9.1

v1.9.0

Compare Source

Uuid::now_v7() is guaranteed to be monotonic

Before this release, Uuid::now_v7() would only use the millisecond-precision timestamp for ordering. It now also uses a global 42-bit counter that's re-initialized each millisecond so that the following will always pass:

let a = Uuid::now_v7();
let b = Uuid::now_v7();

assert!(a < b);

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@1.8.0...1.9.0

v1.8.0

Compare Source

⚠️ Potential Breakage ⚠️

A new impl AsRef<Uuid> for Uuid bound has been added, which can break inference on code like:

let b = uuid.as_ref();

You can fix these by explicitly typing the result of the conversion:

let b: &[u8] = uuid.as_ref();

or by calling as_bytes instead:

let b = uuid.as_bytes();

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@1.7.0...1.8.0

v1.7.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@1.6.1...1.7.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from Clivern as a code owner January 10, 2025 06:43
@renovate renovate bot changed the title Update Rust crate uuid to v1.11.1 Update Rust crate uuid to v1.12.0 Jan 14, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from aa804aa to f0e9af1 Compare January 14, 2025 16:35
@renovate renovate bot changed the title Update Rust crate uuid to v1.12.0 Update Rust crate uuid to v1.12.1 Jan 21, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from f0e9af1 to 6dae3fe Compare January 21, 2025 05:38
@renovate renovate bot changed the title Update Rust crate uuid to v1.12.1 Update Rust crate uuid to v1.13.0 Feb 5, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 6dae3fe to 21987c3 Compare February 5, 2025 04:53
@renovate renovate bot changed the title Update Rust crate uuid to v1.13.0 Update Rust crate uuid to v1.13.1 Feb 5, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 21987c3 to 9e9775b Compare February 5, 2025 08:53
@renovate renovate bot changed the title Update Rust crate uuid to v1.13.1 Update Rust crate uuid to v1.13.2 Feb 18, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch 2 times, most recently from 25e1bfb to ee231ca Compare February 21, 2025 02:06
@renovate renovate bot changed the title Update Rust crate uuid to v1.13.2 Update Rust crate uuid to v1.14.0 Feb 21, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from ee231ca to ef18797 Compare February 26, 2025 06:27
@renovate renovate bot changed the title Update Rust crate uuid to v1.14.0 Update Rust crate uuid to v1.15.0 Feb 26, 2025
@renovate renovate bot changed the title Update Rust crate uuid to v1.15.0 Update Rust crate uuid to v1.15.1 Feb 26, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from ef18797 to 6d1d7df Compare February 26, 2025 22:42
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 6d1d7df to ba8a0a0 Compare March 14, 2025 05:58
@renovate renovate bot changed the title Update Rust crate uuid to v1.15.1 Update Rust crate uuid to v1.16.0 Mar 14, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from ba8a0a0 to 6ed95d9 Compare May 23, 2025 07:03
@renovate renovate bot changed the title Update Rust crate uuid to v1.16.0 Update Rust crate uuid to v1.17.0 May 23, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch 2 times, most recently from 88262b8 to 14d0282 Compare August 11, 2025 15:00
@renovate renovate bot changed the title Update Rust crate uuid to v1.17.0 Update Rust crate uuid to v1.18.0 Aug 11, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 14d0282 to 2a4d073 Compare September 19, 2025 15:54
@renovate renovate bot changed the title Update Rust crate uuid to v1.18.0 Update Rust crate uuid to v1.18.1 Sep 19, 2025
@renovate renovate bot changed the title Update Rust crate uuid to v1.18.1 Update Rust crate uuid to v1.19.0 Dec 2, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 2a4d073 to 62cd007 Compare December 2, 2025 06:05
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 62cd007 to 2249ae6 Compare December 10, 2025 11:16
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 2249ae6 to 5061560 Compare December 31, 2025 17:49
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 5061560 to 017082b Compare January 25, 2026 00:49
@renovate renovate bot changed the title Update Rust crate uuid to v1.19.0 Update Rust crate uuid to v1.20.0 Jan 25, 2026
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch 2 times, most recently from 3b8448e to 43528a1 Compare February 14, 2026 01:52
@renovate renovate bot changed the title Update Rust crate uuid to v1.20.0 Update Rust crate uuid to v1.21.0 Feb 14, 2026
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 43528a1 to 09161cd Compare February 25, 2026 11:01
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 09161cd to 24cd379 Compare March 6, 2026 01:53
@renovate renovate bot changed the title Update Rust crate uuid to v1.21.0 Update Rust crate uuid to v1.22.0 Mar 6, 2026
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 24cd379 to ea7ec8a Compare March 13, 2026 18:04
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from ea7ec8a to 14ad22a Compare March 27, 2026 05:58
@renovate renovate bot changed the title Update Rust crate uuid to v1.22.0 Update Rust crate uuid to v1.23.0 Mar 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants