Bump keccak from 0.1.4 to 0.1.6 in /TicTacToe#830
Bump keccak from 0.1.4 to 0.1.6 in /TicTacToe#830dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [keccak](https://github.com/RustCrypto/sponges) from 0.1.4 to 0.1.6. - [Commits](RustCrypto/sponges@keccak/v0.1.4...keccak-v0.1.6) --- updated-dependencies: - dependency-name: keccak dependency-version: 0.1.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryLow Risk Overview Written by Cursor Bugbot for commit 4256b51. This will update automatically on new commits. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| # This file is automatically @generated by Cargo. | ||
| # It is not intended for manual editing. | ||
| version = 3 | ||
| version = 4 |
There was a problem hiding this comment.
Unintended Cargo.lock format version bump to v4
Low Severity
The Cargo.lock format version was changed from 3 to 4 as an unintended side effect of this dependency bump. Cargo.lock v4 causes a hard parse failure on Rust versions older than 1.78 ("this version of Cargo does not understand this lock file"). While the project's CI uses Rust 1.78.0, which does support v4, this format change is outside the scope of a keccak version bump and may break builds for contributors or tooling on older Rust versions.


Bumps keccak from 0.1.4 to 0.1.6.
Commits
a8936d9keccak v0.1.640c50c1keccak v0.1.5 (#69)2dc13bfkeccak: enable asm backend for p1600 (#68)a3a4e01Revert "Update Cargo.lock" (#67)3a9a29eUpdate Cargo.lock9e4f6bckeccak: don't testsimdfeature inminimal-versionsworkflow (#66)329d4cdReplace cross tests with MIRI (#63)48cc4acbuild(deps): bump actions/checkout from 3 to 4 (#61)651a34ekeccak: replace CI tests on MIPS with PPC32 (#62)4730c6fbenches: remove criterion deps workaround (#60)Dependabot 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)You can disable automated security fix PRs for this repo from the Security Alerts page.