chore(deps): bump uuid from 1.12.1 to 1.23.4

[dependabot]

Bumps uuid from 1.12.1 to 1.23.4.

Release notes

Sourced from uuid's releases.

v1.23.4

What's Changed

• Fix up name of fuzz script in readme by @​KodrAus in uuid-rs/uuid#888
• document fixes by @​frostyplanet in uuid-rs/uuid#889
• Prepare for 1.23.4 release by @​KodrAus in uuid-rs/uuid#890

New Contributors

• @​frostyplanet made their first contribution in uuid-rs/uuid#889

Full Changelog: uuid-rs/uuid@v1.23.3...v1.23.4

v1.23.3

What's Changed

• Fix up parser panic on empty input by @​KodrAus in uuid-rs/uuid#886
• Prepare for 1.23.3 release by @​KodrAus in uuid-rs/uuid#887

Full Changelog: uuid-rs/uuid@v1.23.2...v1.23.3

v1.23.2

What's Changed

• Improve error messages for ambiguous formats by @​KodrAus in uuid-rs/uuid#882
• Prepare for 1.23.2 release by @​KodrAus in uuid-rs/uuid#883

Full Changelog: uuid-rs/uuid@v1.23.1...v1.23.2

v1.23.1

What's Changed

• Remove deprecated msrv feature from wasm-bindgen dependency by @​guybedford in uuid-rs/uuid#877
• fix: Timestamp::from_gregorian deprecation note by @​aznashwan in uuid-rs/uuid#878
• Prepare for 1.23.1 release by @​KodrAus in uuid-rs/uuid#879

New Contributors

• @​guybedford made their first contribution in uuid-rs/uuid#877
• @​aznashwan made their first contribution in uuid-rs/uuid#878

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

v1.23.0

What's Changed

• feat: add support for 'hyphenated' format in the serde module by @​FrenchDilettante in uuid-rs/uuid#865
• Fix a number of bugs in time-related code by @​KodrAus in uuid-rs/uuid#872
• Reword invalid char error message by @​KodrAus in uuid-rs/uuid#873
• Impl cleanups by @​KodrAus in uuid-rs/uuid#874
• Use LazyLock to synchronize v1/v6 context initialization by @​KodrAus in uuid-rs/uuid#875
• Prepare for 1.23.0 release by @​KodrAus in uuid-rs/uuid#876

New Contributors

• @​FrenchDilettante made their first contribution in uuid-rs/uuid#865

... (truncated)

Commits

• 3296d64 Merge pull request #890 from uuid-rs/cargo/v1.23.4
• cba53d0 prepare for 1.23.4 release
• e347af4 Merge pull request #889 from frostyplanet/main
• e9bf55c doc: Fix broken link warnings
• 5351af4 doc: Enable feature flag label for docs.rs
• 1e6a966 Merge pull request #888 from uuid-rs/KodrAus-patch-1
• c9619f6 fix up name of fuzz script in readme
• 20da78b Merge pull request #887 from uuid-rs/cargo/v1.23.3
• 62232ca prepare for 1.23.3 release
• 2320c6a Merge pull request #886 from uuid-rs/fix/parser-panics
• Additional commits viewable in compare view

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6fecd9be64

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep UUID generation working in Node wasm

Cargo.toml still enables uuid on wasm with only features = ["v4", "v7", "js"], and README's wasm support list does not mark uuid_v4/uuid_v7 unsupported. With this lock bump, those functions no longer use uuid 1.12's getrandom 0.2 js backend, which fell back to Node's crypto.randomFillSync; uuid 1.23's js RNG only calls globalThis.crypto.getRandomValues, so wasm bundles running under Node/CommonJS or other JS hosts without that global now panic at UUID generation. Please either keep a Node-compatible UUID RNG for wasm or document these functions as unsupported in that environment.

Useful? React with 👍 / 👎.