Skip to content

chore(deps): update rust crates#24192

Merged
camc314 merged 1 commit into
mainfrom
renovate/rust-crates
Jul 5, 2026
Merged

chore(deps): update rust crates#24192
camc314 merged 1 commit into
mainfrom
renovate/rust-crates

Conversation

@renovate

@renovate renovate Bot commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
num-bigint workspace.dependencies minor 0.4.60.5.0
rustc-hash workspace.dependencies patch 2.1.22.1.3

Release Notes

rust-num/num-bigint (num-bigint)

v0.5.1

Compare Source

Contributors: @​cuviper

v0.5.0

Compare Source

  • Upgrade to rand v0.10 and/or v0.9, and split rand_core.
    • The former rand feature is now split into multiple features, rand_0_9,
      rand_core_0_9, rand_0_10, and rand_core_0_10, depending on the
      version and feature set you need.
    • The RandBigInt extension trait is now split into BigRng09 and
      BigRng010 for each version.
    • The gen_* methods are deprecated in favor of new random_* methods.
    • This is also a value-breaking release, as rand defines it.

Contributors: @​bionicles, @​cuviper, @​divergentdave

v0.4.8

Compare Source

Contributors: @​cuviper

v0.4.7

Compare Source

Contributors: @​cp289, @​cuviper, @​hkalbasi, @​mikem8891, @​pRizz, @​tyilo, @​xtqqczze


Configuration

📅 Schedule: (in timezone Asia/Shanghai)

  • Branch creation
    • "before 10am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/rust-crates branch from 0448284 to 753e0dd Compare July 5, 2026 17:24
@codspeed-hq

codspeed-hq Bot commented Jul 5, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 62 untouched benchmarks
⏩ 9 skipped benchmarks1


Comparing renovate/rust-crates (753e0dd) with main (1b13f38)2

Open in CodSpeed

Footnotes

  1. 9 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

  2. No successful run was found on main (8853f14) during the generation of this report, so 1b13f38 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

@camc314
camc314 merged commit ef33878 into main Jul 5, 2026
39 checks passed
@camc314
camc314 deleted the renovate/rust-crates branch July 5, 2026 17:35
leaysgur added a commit that referenced this pull request Jul 6, 2026
`num-bigint` 0.4.6 → 0.5.1 (#24192) reduced heap allocations when
parsing BigInt literals. `kitchen-sink.tsx` is the only tracked fixture
containing BigInt literals, so its parser row changed: 2058 → 2051 sys
allocs (an improvement, not a regression).

The snapshot went stale on main because the Allocations job's change
filter (`check-changes.js`) skips the measurement when no files under
`crates/` changed — a `Cargo.lock`-only dependency update never
re-measures. The mismatch then surfaces on any unrelated PR that touches
the snapshot paths (currently blocking #24098).

Verified by bisecting locally: parent commits of #24192 measure 2058,
#24192 and current main measure 2051, matching CI exactly.

The same filter gap affects Conformance, Minsize, and Linter timings
jobs; a follow-up may address the filter itself.
graphite-app Bot pushed a commit that referenced this pull request Jul 6, 2026
…nges (#24199)

### Summary

The include-mode filter in `check-changes.js` short-circuits to "skip" when no changed files are under `crates/`, so it never reaches the cargo tree dependency check for `Cargo.lock`-only dependency updates or `rust-toolchain.toml` bumps. Conformance, Minsize, Allocations, and Linter timings are all gated on this filter.

This is how #24192 (`num-bigint` 0.4.6 → 0.5.1) landed with a stale parser allocation snapshot: the update changed BigInt-literal parsing allocation counts, the Allocations job never re-measured on main, and the mismatch surfaced on an unrelated PR (#24098). The snapshot itself is fixed in #24198.

This PR treats `Cargo.lock` and `rust-toolchain.toml` changes as affecting every crate, so measurement jobs always re-run on dependency and toolchain updates. The cost is that renovate dependency PRs now run these four jobs; dependency updates are exactly the class of change that can shift measured behavior, so that is the intended behavior. Exclude-mode and paths-only jobs are unaffected (exclude mode already runs on such changes by construction).

### Trade-off

For Conformance specifically this closes a correctness gap, not just a snapshot-staleness one: a dependency update that changes parser/transformer behavior currently skips conformance entirely.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant