Bencher

v0.6.11 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 1d Pipelines

✓ No known CVEs patched

✓ No known CVEs patched in this version

Topics

benchmark benchmarking ci-cd code-quality continuous-benchmarking performance

Affected surfaces

breaking_upgrade

Summary

AI summary

BREAKING CHANGE: GitHub Check names now include the project name to prevent overwriting across projects.

Full changelog

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)

GitHub Check name now includes the project name (e.g., "Bencher Report (ProjectName)") to avoid overwriting; `--ci-id` can override, and in‑progress checks fallback to "Bencher Report" when `--project` is unset. Update branch protection rules accordingly.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Bencher

Get notified when new releases ship.

About Bencher

Suite of continuous benchmarking tools designed to catch performance regressions in CI.