[dependabot]

Bumps the cargo group with 1 update: smallvec.

Updates smallvec from 1.16.4 to 1.16.5

Release notes

Sourced from smallvec's releases.

v1.16.5

What's Changed

• ci: port v2 CI to v1 by @​alejandro-vaz in smallvec/smallvec#853

Full Changelog: smallvec/smallvec@v1.16.4...v1.16.5

Commits

• 6e90005 ci: port v2 CI to v1 (#853)
• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Speed against 8e088cd1

Measured on AMD EPYC 9V45 96-Core Processor.
Both sides built with rustc 1.99.1 (58cf8f9c3 2026-10-13).

Both sides built and run on this runner in this job, the way
scripts/speed.sh measures a perf commit. Each round runs
both sides on a layout of its own, the same compiled code with
its code and data shuffled and moved, so the 95% interval carries
where the code landed as well as the run. The verdict holds the
interval against a 1% threshold. The default layout, the one a
release ships, is measured after as a diagnostic. The node
counts are the search's: they move when the search does, and a
speed change leaves them alone.

round     base nps  candidate nps  change
    1      5913514        5751224   -2.7%
    2      6042131        5881286   -2.7%
    3      5995892        6170419   +2.9%
    4      6061838        6097953   +0.6%
    5      6195633        6442494   +4.0%
    6      5855305        6325112   +8.0%
    7      5834518        6052801   +3.7%
    8      6089639        5682223   -6.7%
    9      5923968        6094544   +2.9%
   10      6117574        6092410   -0.4%
   11      6169620        6141516   -0.5%
   12      6215361        6246840   +0.5%
   13      6035793        5939362   -1.6%
   14      6121210        6371492   +4.1%
   15      6107967        6121414   +0.2%
   16      6063849        6221377   +2.6%
   17      5802543        5928772   +2.2%
   18      5856743        5716949   -2.4%
   19      6003604        6204075   +3.3%
   20      5986801        6081736   +1.6%
   21      6029780        6017041   -0.2%
   22      6023845        6080243   +0.9%
   23      5988332        5997470   +0.2%
   24      6049397        6028440   -0.3%
   25      6046254        6198740   +2.5%
   26      5976952        5943654   -0.6%
   27      5870355        5856821   -0.2%
   28      6081643        5939812   -2.3%
   29      6052764        5984450   -1.1%
   30      6123311        5921389   -3.3%
   31      5792083        6093933   +5.2%
   32      5938521        6012430   +1.2%
   33      5973923        5897935   -1.3%
   34      5919839        5781958   -2.3%
   35      5941719        5861978   -1.3%
   36      5977096        5832388   -2.4%
   37      5512351        5745828   +4.2%
   38      5992985        5897927   -1.6%
   39      5920174        6128645   +3.5%
   40      5917379        5897892   -0.3%

              nodes    time  median nps  faster half
base       11916992  1.99 s     5994438      6081355
candidate  11916992  1.98 s     6014736      6160561
change                            +0.3%        +1.3%

paired change +0.4%, 95% interval -0.5% to +1.3%
diagnostic, on the default layout alone -0.9%, 95% interval -5.8% to +1.3%, 13 rounds

not resolved: the interval reaches past ±1.0% without clearing it, so
more rounds are needed to say either way

Speed: +0.4% (bench nps, 95% interval -0.5% to +1.3%, 40 interleaved rounds over shuffled layouts vs 8e088cd1)

The instructions each side's bench executed, counted under
cachegrind. The count repeats to within a few hundred
instructions, so a small change here is a real one, but it
prices instructions only: cache misses, mispredicted branches
and where the code lands are the speed's to show.

instructions against 8e088cd1, one cachegrind run a side, bench

             instructions     nodes  per node
base       15,968,705,908  11916992    1340.0
candidate  15,968,705,907  11916992    1340.0
change             -0.00%              -0.00%

within ±0.7%, as far as edits not made for speed have moved the count