Bump uuid from 1.23.5 to 1.24.0 in /src-tauri#35
Conversation
Bumps [uuid](https://github.com/uuid-rs/uuid) from 1.23.5 to 1.24.0. - [Release notes](https://github.com/uuid-rs/uuid/releases) - [Commits](uuid-rs/uuid@v1.23.5...v1.24.0) --- updated-dependencies: - dependency-name: uuid dependency-version: 1.24.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d65a57bcc3
ℹ️ 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".
| [[package]] | ||
| name = "uuid" | ||
| version = "1.23.5" | ||
| version = "1.24.0" |
There was a problem hiding this comment.
This bump changes the locked Rust component to uuid 1.24.0, but THIRD_PARTY_LICENSES_RUST.txt still only reports uuid 1.23.5. The repo's Rust license check builds the locked Cargo tree and fails on missing reported components, and the release docs require this generated report to track src-tauri/Cargo.lock; as-is, release/legal CI will treat the third-party inventory as stale until the Rust license report is regenerated.
Useful? React with 👍 / 👎.
Bumps uuid from 1.23.5 to 1.24.0.
Release notes
Sourced from uuid's releases.
Commits
6a8aeabMerge pull request #896 from uuid-rs/cargo/v1.24.0e6db8ecprepare for 1.24.0 release606f236Merge pull request #892 from weifanglab/mainab848dbfeat(fmt): support encoding into MaybeUninit buffers6fa1a1efeat(fmt): support encoding into MaybeUninit buffersDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)