build(deps): bump bencherdev/bencher from 0.6.6 to 0.6.11

[dependabot]

Bumps bencherdev/bencher from 0.6.6 to 0.6.11.

Release notes

Sourced from bencherdev/bencher's releases.

v0.6.11

• Fix the percent difference shown in the report table when a metric drops to zero; a value of 0.00 against a positive baseline now shows -100.00% instead of 0.00% in both the Console and the CI comment (Thank you @​OmarTawfik)
• BREAKING CHANGE Name the GitHub Check after the Project (ie Bencher Report (<PROJECT NAME>)) so runs for different Projects on the same commit no longer overwrite each other; --ci-id takes the Project name's place when set, the in-progress Check falls back to Bencher Report until the results are posted when --project is not set, and the name is truncated to 255 bytes. Update any required status check named Bencher Report in branch protection to the new name, and note that renaming a Project changes the Check name too (Thank you @​OmarTawfik)

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

v0.6.8

• BREAKING CHANGE Change the default self-hosted API server port from 61016 to the newly IANA-registered 6610. Deployments relying on the default now serve the API on 6610. Update clients, reverse proxies, and --host/BENCHER_HOST references (Docker Compose, devcontainer, and docs are updated to match). To stay on 61016, set server.bind_address to 0.0.0.0:61016 (or run bencher up --api-port 61016).
• Mark the remaining user API token REST endpoints (list, view, update, and revoke) as deprecated in the OpenAPI spec and API docs; they continue to work for existing tokens

v0.6.7

• Fix the OCI registry token endpoint for the Docker 29+ containerd image store, which sends multiple scope query parameters and an OAuth2 POST token exchange (Thank you @​travishathaway)
• Add user-scoped API keys (bencher_user_...) that authenticate as the owning user across every endpoint a JWT can reach, including docker login; the one exception is key management: a user API key cannot create more keys and can only see, update, or revoke itself, so a leaked key cannot mint credentials that outlive its own revocation, tamper with the user's other keys, or enumerate them
• Add bencher user key {create,list,view,update,revoke} CLI subcommands and an "API Keys" page in the Console for managing user API keys
• --key/BENCHER_API_KEY now accepts either a project-scoped key (bencher_run_*) or a user-scoped key (bencher_user_*); the --project requirement applies only to project-scoped keys
• DEPRECATED User API tokens are deprecated in favor of user API keys: POST /v0/users/{user}/tokens (bencher token create) now always fails with a 403 Forbidden error; existing API tokens continue to work and can still be listed, viewed, renamed, and revoked
• Replace the Tokens entry in the Console account dropdown with Keys, and hide the "API Tokens" page entirely for accounts created after 15 June 2026
• bencher run --github-actions now always creates a Bencher Report GitHub Check (failing on an active Alert), so it can be used as a required status check in branch protection; the check is created on a best effort basis, so check creation failures are now warnings instead of errors (Thank you @​OmarTawfik)
• Create the GitHub Check on the pull request head commit (pull_request.head.sha or workflow_run.head_sha) instead of GITHUB_SHA, so the check appears on the pull request
• Append the --ci-id ID to the GitHub Check name (ie Bencher Report (<ID>)) so multiple bencher run invocations on the same commit get distinct, stable check names

Commits

• 4c83b25 Release v0.6.11
• 3e5c8c0 Name the GitHub Check after the Project (#958)
• 0b295d1 Bump Claude Code review CI to Opus 5 (#959)
• 3b87c27 Fix report table percent difference when a metric drops to zero (#957)
• 2224442 advisorModel
• 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)
• 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 this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)