chore(deps): Bump criterion from 0.5.1 to 0.8.2#53
Conversation
Bumps [criterion](https://github.com/criterion-rs/criterion.rs) from 0.5.1 to 0.8.2. - [Release notes](https://github.com/criterion-rs/criterion.rs/releases) - [Changelog](https://github.com/criterion-rs/criterion.rs/blob/master/CHANGELOG.md) - [Commits](criterion-rs/criterion.rs@0.5.1...criterion-v0.8.2) --- updated-dependencies: - dependency-name: criterion dependency-version: 0.8.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
The criterion 0.8 bump itself is good: I verified atlas-spark-bench --benches --tests compiles cleanly against criterion 0.8.2 / criterion-plot 0.8.2, so the API change is absorbed with no code edits needed. The only blocker is that this branch's Cargo.lock has drifted behind main (a cargo build --locked on the merge result fails because the lock is missing the new transitive deps like alloca/page_size). Regenerating the lock against current main will make it mergeable. @dependabot rebase |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
Dependabot's #53 only bumped atlas-spark-bench, but xgrammar also depends on criterion, so the lock could not resolve (xgrammar pinned ^0.5 while atlas-spark-bench wanted 0.8). Bump both crates and regenerate only the criterion + criterion-plot lock entries (targeted, no incidental dep churn). Verified the xgrammar and atlas-spark-bench bench/test suites compile against criterion 0.8.2 with no API changes needed. Benchmark-only dev-dependency, zero runtime impact. Co-authored-by: Azeez Ishaqui <debaterishaqui@gmail.com>
|
Superseded by the completed bump in the PR above: your bump was correct but only touched atlas-spark-bench, and xgrammar also depends on criterion, so the lock could not resolve until both were moved to 0.8 together. Folded both in and verified the bench suites compile against 0.8.2. Thanks dependabot. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps criterion from 0.5.1 to 0.8.2.
Release notes
Sourced from criterion's releases.
... (truncated)
Changelog
Sourced from criterion's changelog.
... (truncated)
Commits
7f0d745chore: release v0.8.24a467cechore(deps): bump crate-ci/typos from 1.40.0 to 1.43.0b277a75Fix panic with uniform iteration durations in benchmarks828af14fix: don't build alloca on unsupported targetsb01316bUpdate Readme4c02a3bExclude development scripts from published packagee4e06dfchore: release v0.8.1aa548b9fix: Homepage link950c3b7fix: Typo7e3e50cchore(deps): bump crate-ci/typos from 1.23.5 to 1.40.0Dependabot 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)