Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 10, 2024

This PR contains the following updates:

Package Type Update Change
uuid dependencies minor 1.6.1 -> 1.18.1

Release Notes

uuid-rs/uuid (uuid)

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 - "after 1pm and before 5pm on Friday" in timezone Asia/Tokyo, 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.

@codecov-commenter
Copy link

codecov-commenter commented May 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 19.76%. Comparing base (c1abb90) to head (2f27ec7).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #41   +/-   ##
=======================================
  Coverage   19.75%   19.76%           
=======================================
  Files         100       99    -1     
  Lines        4899     4998   +99     
=======================================
+ Hits          968      988   +20     
- Misses       3931     4010   +79     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 2d0e3eb to 422e3f6 Compare June 24, 2024 06:52
@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 from 422e3f6 to f13ac74 Compare June 24, 2024 23:26
@renovate renovate bot changed the title ⬆️ - Update Rust crate uuid to v1.9.0 ⬆️ - Update Rust crate uuid to v1.9.1 Jun 24, 2024
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from f13ac74 to 2f27ec7 Compare July 9, 2024 04:40
@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
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 2f27ec7 to 1864c57 Compare October 16, 2024 07:29
@renovate renovate bot changed the title ⬆️ - Update Rust crate uuid to v1.10.0 ⬆️ - Update Rust crate uuid to v1.11.0 Oct 16, 2024
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 1864c57 to fb72c24 Compare January 10, 2025 06:38
@renovate renovate bot changed the title ⬆️ - Update Rust crate uuid to v1.11.0 ⬆️ - Update Rust crate uuid to v1.11.1 Jan 10, 2025
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from fb72c24 to e0c9826 Compare January 14, 2025 14:29
@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 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 e0c9826 to 6493267 Compare January 21, 2025 05:16
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 6493267 to c05c861 Compare February 5, 2025 04:51
@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 c05c861 to eb06f9a Compare February 5, 2025 10:57
@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 eb06f9a to 7a412eb Compare February 18, 2025 02:00
@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 from 7a412eb to 6170a09 Compare February 21, 2025 19:51
@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 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 force-pushed the renovate/uuid-1.x-lockfile branch from 6170a09 to f434cfb Compare February 26, 2025 06:19
@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 f434cfb to 8faf54b Compare February 26, 2025 22:26
@renovate renovate bot force-pushed the renovate/uuid-1.x-lockfile branch from 8faf54b to 286af63 Compare March 14, 2025 06:37
@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 286af63 to 9c30b59 Compare May 23, 2025 02:48
@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 f4d7db2 to 39c52af Compare August 11, 2025 13:34
@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 39c52af to 40aa717 Compare September 6, 2025 22:50
@renovate renovate bot changed the title ⬆️ - Update Rust crate uuid to v1.18.0 ⬆️ - Update Rust crate uuid to v1.18.1 Sep 6, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Sep 25, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path kernel/Cargo.toml --package [email protected] --precise 1.18.1
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 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.

2 participants