build(deps): bump the default group across 1 directory with 2 updates

[dependabot]

Bumps the default group with 2 updates in the / directory: bencherdev/bencher and astral-sh/setup-uv.

Updates bencherdev/bencher from 0.6.8 to 0.6.10

Release notes

Sourced from bencherdev/bencher's releases.

v0.6.10

• Add a Y-Axis scale toggle to perf plots with three modes (Auto, Linear, and Log); the Auto default preserves the existing adaptive scaling, Log falls back to Auto when the data includes zero or negative values, and the selection is saved in the plot URL, restored for pinned plots, and can be set with bencher plot create --y-axis or changed with bencher plot update --y-axis
• Selecting a pinned plot from the Plots tab in the Perf explorer now applies the plot's saved X-Axis and Y-Axis instead of the defaults
• Thin the Branch Version Number x-axis tick labels to fit the plot width; previously every version rendered a label, which overlapped into an unreadable smear on plots with many versions
• Add Bencher MCP, a hosted Model Context Protocol server at https://mcp.bencher.dev/mcp (/mcp on Self-Hosted); AI agents and assistants can query benchmark data and submit runs with the same permissions as a project API key (bencher_run_*), without needing the bencher CLI installed

v0.6.9

• Add Vitest adapter (js_vitest)
• Add a database.cache_size server config option for the writer connection page cache in KiB (default 64 MiB)
• Update a pinned plot in place with PATCH /v0/projects/{project}/plots/{plot}, the Perf explorer "Update Pin" button, or bencher plot update
• Reject plot dimension UUIDs from other projects with a 404 Not Found and empty dimension lists with a 400 Bad Request
• Add the project name and link as the first row of the PR comment report table (Thank you @​OmarTawfik)
• Create the GitHub Check with an in_progress status before benchmarks run and complete it with the results once they finish, so reruns no longer show a stale conclusion; if bencher run exits with an error before the results are posted, the check is marked as failed (Thank you @​OmarTawfik)
• Add runner update channels via runner up --update-channel <stable|canary> (default: stable); the canary channel tracks a rolling prerelease that is rebuilt whenever the runner changes on a Bencher Cloud deploy, so runner changes are field-tested on Bencher Cloud before a versioned release; canary runners report their binary checksum and converge on the published build by content rather than by version
• Runner self-update checksum fetch failures no longer drop the WebSocket channel into a reconnect loop; the server now logs the failure, skips the update offer, and retries at the runner's next ready poll
• BREAKING CHANGE The reports list endpoint (GET /v0/projects/{project}/reports) now omits the results and alerts for each report by default, drastically reducing response sizes for projects with large reports; set the new expand query param to true (bencher report list --expand) to restore the previous behavior. A new counts field summarizes each report with the number of benchmarks and distinct measures per iteration and the total and active alerts. Note that older CLI versions cannot parse the new default list response, so update the CLI before using bencher report list; bencher run is unaffected

Commits

• d2895af Release v0.6.10
• 99e4069 Fetch console data in parallel with the WASM validator (#941)
• 0e9e229 Add Bencher MCP server (#953)
• c70d150 Sort cargo ops isolate GRUB drop-in after provider drop-ins (#955)
• a50bacf Add cargo ops isolate subcommand for CPU isolation boot args (#954)
• 980ca74 Add a Y-Axis scale toggle to perf plots (#947)
• 8171a99 Decrease run-to-run variance of the bare metal runner (#923)
• bacd5ad Release v0.6.9
• da4f0cf Add Claude Code plugin with Bencher skill (#952)
• ac764f2 Collapse results and alerts by default in the reports list API (#926)
• Additional commits viewable in compare view

Updates astral-sh/setup-uv from 8.3.1 to 9.0.0

Release notes

Sourced from astral-sh/setup-uv's releases.

v9.0.0 🌈 Change prune-cache default to false

Changes

This release disables the default cache cache pruning to ease the load on the PyPi infrastructure. Since users might experience more GitHub Actions cache usage which might result in higher costs this is marked as a breaking change. To read more on why we did this (now) you can read the detailed analysis and reasoning in #967

Besides this big breaking change we also have a small bugfix while building caches for linux distributions that behave a big different than the "big ones" and a speed up in version resolution by only reading the version manifest until a matching version is found saving runtime and network bandwith.

🚨 Breaking changes

• Change prune-cache default to false @​charliermarsh (#967)

🐛 Bug fixes

• fix: fall back to distribution ID when os-release has no version field @​cxzhong (#961)

🚀 Enhancements

• Speed up version client by partial response reads @​eifinger (#807)

🧰 Maintenance

• chore: update known checksums for 0.11.30 @github-actions[bot] (#968)
• chore: update known checksums for 0.11.29 @github-actions[bot] (#960)

📚 Documentation

• docs: update version references to v8.3.2 @github-actions[bot] (#949)

⬆️ Dependency updates

• chore(deps): roll up Dependabot updates @​eifinger (#970)
• chore(deps): roll up Dependabot updates @​eifinger (#962)

Commits

• c771a70 chore(deps): roll up Dependabot updates (#970)
• 2f537ca chore: update known checksums for 0.11.30 (#968)
• 2269552 Speed up version client by partial response reads (#807)
• 47a7f4f Change prune-cache default to false (#967)
• 71966ef chore(deps): roll up Dependabot updates (#962)
• f12b1f0 fix: fall back to distribution ID when os-release has no version field (#961)
• ecd24dd chore: update known checksums for 0.11.29 (#960)
• 6a19136 docs: update version references to v8.3.2 (#949)
• 11f9893 chore: roll up Dependabot updates (#948)
• f798556 docs: update version references to v8.3.1 (#946)
• Additional commits viewable 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