Skip to content

Lock file maintenance - #10788

Merged
robert3005 merged 1 commit into
developfrom
renovate/lock-file-maintenance-rust-lock-file-maintenance
Oct 27, 2026
Merged

robert3005 merged 1 commit into
developfrom
renovate/lock-file-maintenance-rust-lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 added the changelog/chore A trivial change label Oct 26, 2026
@codspeed

codspeed Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Merging this PR will regress 3 benchmarks

3 warnings, 1 note

⚠️ Walltime results may be unreliable

Some benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.

Learn more about Macro Runners

See affected benchmarks

⚠️ Unable to measure the execution of 2 benchmarks

These benchmarks measured no execution time, so their results are not comparable and count as unchanged. This usually happens when the compiler removes the code under test.

Prevent compiler optimizations

See affected benchmarks

⚠️ 19 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

ℹ️ 40 benchmarks have no flamegraph

The flamegraph wasn't generated: the symbols of the profiling trace could not be resolved, because no information about the language frames was collected.

See affected benchmarks

⚡ 19 improved benchmarks
❌ 3 regressed benchmarks
✅ 2417 untouched benchmarks
⏩ 166 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ CPU Simulation chunked_dict_primitive_canonical_into[f64, (1000, 1000, 10)] 146.7 µs 200.6 µs -26.84%
❌ CPU Simulation encode_primitives[f32, (1000, 2)] 118.3 µs 146.6 µs -19.35%
❌ CPU Simulation compare[1] 111.6 µs 133.3 µs -16.32%
⚡ Walltime threshold_neon[8] 2.6 µs 1.3 µs +92.51%
⚡ Walltime threshold_neon[64] 3.8 µs 2.5 µs +48.36%
⚡ CPU Simulation bench_compare_varbin[(10000, 128)] 99.8 µs 70.3 µs +41.93%
⚡ Walltime threshold_neon[80] 4.8 µs 3.4 µs +41.5%
⚡ Walltime filter_neon[64] 2.4 µs 1.7 µs +36.91%
⚡ CPU Simulation bench_compare_varbin[(50000, 2)] 164 µs 123.3 µs +33.02%
⚡ Walltime filter_neon[8] 1,203 ns 929 ns +29.49%
⚡ Walltime starts_with_avx512[8, VarBinView] 86.7 µs 69.5 µs +24.79%
⚡ Walltime filter_neon[80] 3 µs 2.5 µs +23.87%
⚡ CPU Simulation bench_compare_varbin[(50000, 4)] 164.1 µs 134 µs +22.53%
⚡ CPU Simulation bench_compare_varbin[(50000, 8)] 165.1 µs 134.8 µs +22.47%
⚡ CPU Simulation bench_compare_varbin[(50000, 128)] 167.5 µs 136.8 µs +22.38%
⚡ CPU Simulation bench_compare_varbin[(50000, 32)] 165.1 µs 135.1 µs +22.27%
⚡ CPU Simulation bench_compare_sliced_dict_varbinview[(7500, 10000)] 230 µs 192.9 µs +19.25%
⚡ CPU Simulation bench_compare_sliced_dict_varbinview[(10000, 10000)] 236.2 µs 199.2 µs +18.58%
⚡ CPU Simulation compare[1] 154.7 µs 132.1 µs +17.09%
⚡ CPU Simulation bench_compare_varbin[(50000, 512)] 216.6 µs 186.2 µs +16.33%
... ... ... ... ... ...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing renovate/lock-file-maintenance-rust-lock-file-maintenance (10d4a82) with develop (db0c700)

Open in CodSpeed

Footnotes

  1. 166 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. ↩

@renovate renovate Bot changed the title chore(deps): lock file maintenance Lock file maintenance Oct 26, 2026
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance-rust-lock-file-maintenance branch 2 times, most recently from 45a2c3a to f047203 Compare October 26, 2026 19:08
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance-rust-lock-file-maintenance branch from f047203 to 10d4a82 Compare October 27, 2026 11:04
@robert3005
robert3005 enabled auto-merge (squash) October 27, 2026 11:08
@robert3005
robert3005 merged commit 92bee27 into develop Oct 27, 2026
85 of 86 checks passed
@robert3005
robert3005 deleted the renovate/lock-file-maintenance-rust-lock-file-maintenance branch October 27, 2026 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/chore A trivial change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant