Conversation
Greptile SummaryThis PR refreshes Confidence Score: 4/5Safe to merge once the large aube CI-warm and Bun add-dependency improvements are spot-checked against raw run data. No code defects found; all numbers are internally self-consistent. Score is 4 rather than 5 because benchmark PRs carry inherent unverifiability — the two unusually large deltas (−66% CI warm, −60% Bun add) warrant a manual cross-check of the raw hyperfine output as the PR itself recommends. benchmarks/results.json — specifically the ci-warm and add scenario values for aube and Bun. Important Files Changed
Reviews (1): Last reviewed commit: "chore: refresh benchmarks" | Re-trigger Greptile |
Benchmark changesPublic ratios: warm installs vs Bun 4x -> 8x; warm installs vs pnpm 7x -> 11x.
6850c8b vs 51e6a9c | aube/bun/pnpm | 3 scenarios | 3 runs | 500mbit/50ms | generated by Codex. |
🤖 Refreshed benchmarks
benchmarks/results.jsonwas pinned to aube1.5.2; the workspace is now1.5.2. Re-ranmise run bench:bumpon the hermetic Verdaccio registry (500mbit / 50ms per the mise task) and regeneratedbenchmarks/results.jsonplus the READMEBENCH_RATIOSblock. The benchmark matrix pins aube's GVS mode vianpm_config_enable_global_virtual_store=true|false(the auto-synthesized env alias for theenableGlobalVirtualStoresetting), so GitHub Actions' inheritedCI=trueenvironment does not change whether aube runs with GVS enabled or disabled.Benchmark changes
Public ratios: warm installs vs Bun 4x -> 5x; warm installs vs pnpm 7x -> 6x; repeat test vs Bun 4x -> 3x; repeat test vs pnpm 34x -> 28x.
Review the numbers before merging — if anything looks wildly off vs. the previous release, investigate before landing. Hermetic proxy jitter or an npmjs uplink hiccup can occasionally skew results.
Once merged to main, the updated bench results flow into the next
release-plz-prrun automatically.Generated by the
bench-refreshworkflow.