Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Rust crate uuid to v1.10.0 #18

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 5, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
uuid dependencies minor 1.6.1 -> 1.10.0

Release Notes

uuid-rs/uuid (uuid)

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 May 5, 2024 11:27
@renovate renovate bot changed the title Update Rust crate uuid to v1.8.0 Update Rust crate uuid to v1.9.0 Jun 24, 2024
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch 2 times, most recently from 7df0843 to 7b37758 Compare June 25, 2024 00:28
@renovate renovate bot changed the title Update Rust crate uuid to v1.9.0 Update Rust crate uuid to v1.9.1 Jun 25, 2024
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 7b37758 to 470d708 Compare July 9, 2024 04:14
@renovate renovate bot changed the title Update Rust crate uuid to v1.9.1 Update Rust crate uuid to v1.10.0 Jul 9, 2024
@Clivern Clivern closed this Aug 26, 2024
Copy link
Contributor Author

renovate bot commented Aug 26, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (1.6.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/uuid-1.x-lockfile branch August 26, 2024 17:17
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.

1 participant