Skip to content

Bencher

v0.6.6 Breaking

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

Published 17d Pipelines
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

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

Affected surfaces

auth

Summary

AI summary

BREAKING CHANGE: Rename usage to metrics in the organization usage API response and add runner_minutes field.

Full changelog
  • Show context-aware auth hints in API 404 errors: routes that accept project API keys now mention both API tokens and project keys, while token-only routes mention only API tokens
  • BREAKING CHANGE Rename usage to metrics in the organization usage API response and add runner_minutes field for bare metal runner minutes usage
  • Add --max-retry-after CLI option to cap exponential backoff between retries (default 30s) and increase default --attempts from 10 to 35 for ~15 minutes of retry coverage

Breaking Changes

  • Rename `usage` to `metrics` in the organization usage API response and add `runner_minutes` field for bare metal runner minutes usage

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.

Sign up free

About Bencher

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

All releases →

Related context

Beta — feedback welcome: [email protected]