Repository navigation
chore: refresh benchmarks for v1.23.0 - #922
Conversation
![release-plz[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
📝 WalkthroughWalkthroughBenchmark results in ChangesBenchmark Data Refresh
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Greptile SummaryRefreshes the benchmark data from aube 1.22.0 to 1.23.0, updating
Confidence Score: 5/5Benchmark data refresh with no logic or code changes — safe to merge once the numbers have been eyeballed. Both changed files are pure data/prose. The JSON values are internally consistent (integer values match stats.mean rounded to ms, stddev/min/max are plausible for the stated run conditions), the version bumps match the PR description, and all four marketing ratios in the README cross-check correctly against the new JSON figures. The cold-cache regression for aube (+11%) and the across-the-board slowdown of other managers are both acknowledged in the PR description and fall within the variance expected from the hermetic proxy setup. No files require special attention — spot-check the cold-cache row if the +11% aube regression (~6.8s → 7.6s) looks surprising for the 1.23.0 release. Important Files Changed
Reviews (1): Last reviewed commit: "chore: refresh benchmarks" | Re-trigger Greptile |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@benchmarks/results.json`:
- Around line 13-19: In the benchmarks/results.json file, the aube version value
is incorrectly set to 1.23.0 when it should be 1.22.0 according to the latest
released version as of June 2026. Locate the aube property in the JSON object
and change its version string from 1.23.0 to 1.22.0.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Central YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro Plus
Run ID: 8e6cdb0b-834b-43d4-a9e8-7816db2b0b1f
📒 Files selected for processing (2)
README.mdbenchmarks/results.json
| "aube": "1.23.0", | ||
| "bun": "1.3.14", | ||
| "deno": "2.8.3", | ||
| "pnpm": "11.7.0", | ||
| "pnpm": "11.8.0", | ||
| "npm": "11.9.0", | ||
| "yarn": "4.17.0", | ||
| "node": "24.14.0" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What is the latest released version of aube as of June 2026?
💡 Result:
As of June 22, 2026, the latest released version of aube, a fast Node.js package manager, is v1.22.0 [1][2]. This version was released on June 17, 2026, and includes features such as scoped registry tokens and a pnpm-lockfile parity sweep [1].
Citations:
- 1: https://github.com/jdx/aube/releases/tag/v1.22.0
- 2: https://github.com/jdx/aube/releases
🌐 Web query:
What is the latest released version of pnpm as of June 2026?
💡 Result:
As of June 22, 2026, the latest released version of pnpm is 11.8.0 [1].
Citations:
Update aube version from 1.23.0 to 1.22.0 — The latest released version of aube as of June 2026 is v1.22.0, not 1.23.0. The pnpm version (11.8.0) is accurate and current.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@benchmarks/results.json` around lines 13 - 19, In the benchmarks/results.json
file, the aube version value is incorrectly set to 1.23.0 when it should be
1.22.0 according to the latest released version as of June 2026. Locate the aube
property in the JSON object and change its version string from 1.23.0 to 1.22.0.
🤖 Refreshed benchmarks
benchmarks/results.jsonwas pinned to aube1.22.0; the workspace is now1.23.0. 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
Versions:
Public ratios: warm installs vs Bun 1.8x -> 2x; warm installs vs pnpm 3x -> 5x; repeat test vs Bun 8x -> 4x; repeat test vs pnpm 42x -> 34x.
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.Note
Low Risk
Documentation and benchmark artifact updates only; no runtime or install logic changes.
Overview
Re-runs the hermetic benchmark suite and replaces
benchmarks/results.jsonso pinned tool versions match the current release (aube 1.23.0, pnpm 11.8.0) with a newupdatedtimestamp and refreshed timings for warm/cold install and repeatinstall && testscenarios.Updates the README
BENCH_RATIOSblock to match the new numbers: warm install vs pnpm ~5x (was ~3x), vs Bun ~2x (was ~1.8x); repeat test vs pnpm up to 34x (was 42x), vs Bun up to 4x (was 8x).Reviewed by Cursor Bugbot for commit 310aadc. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
Documentation
Tests