Patch benchmark dependencies for Kimetsu 2.8.0 - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The benchmark's separate lockfile still contained vulnerable
h2andquinn-protoreleases, unsoundanyhow/cxxreleases, and yankedder. This updates those dependencies and aligns the three Kimetsu path dependencies with the 2.8.0 release candidate in Kimetsu PR #45.quinn-proto0.11.15 addresses Dependabot alert #1. The regenerated lockfile also consolidates existing Windows dependency edges. No benchmark scoring or recorded measurement artifacts change.Validation:
cargo audit --jsonreports zero known vulnerabilities, with only the existing informationalpastemaintenance notice.cargo test --locked --offline -j 1 -- --test-threads=1passed 132 tests, zero failures, against the Kimetsu 2.8.0 checkout. The harness uses parent-checkout path dependencies, so this PR requires that companion release candidate.