Skip to content

chore: regenerate coverage metrics - #748

Closed
github-actions[bot] wants to merge 0 commit into
masterfrom
chore/metrics-regen
Closed

chore: regenerate coverage metrics#748
github-actions[bot] wants to merge 0 commit into
masterfrom
chore/metrics-regen

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Auto-regenerated after a release. Coverage only.

Note

Published without a benchmark snapshot: **1.0.2 **

History points are measured on the reference workstation, not here.
Run pnpm metrics and pnpm metrics:history there, then open a
chore(bench): regenerate metrics PR.

Benchmark numbers in this diff are the committed reference-host
measurements, re-emitted unchanged — a shared GitHub runner does not
pin the CPU, and measuring benches here would replace them with
whichever host this job drew.

To refresh benchmarks or the per-version history, run them on the
reference workstation: see "Regenerating metrics" in
.claude/rules/benchmarks.md.

@github-actions
github-actions Bot force-pushed the chore/metrics-regen branch 5 times, most recently from 830184a to dd04b7e Compare July 30, 2026 17:05
@github-actions github-actions Bot changed the title chore: regenerate benchmark + history metrics chore: regenerate coverage metrics Jul 30, 2026
@github-actions
github-actions Bot force-pushed the chore/metrics-regen branch from dd04b7e to 6b1551f Compare July 30, 2026 18:28
@johnleider

Copy link
Copy Markdown
Member

Superseded by #753. This was opened 29 Jul by the pre-#749 workflow and carries a metrics.json derived from GHA-measured benchmarks with the retired _apparatus block. #753 regenerates everything on the reference host with the current _env shape.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant