You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(renovate): turn platform automerge back off - #2063
#2062 switched Renovate to GitHub auto-merge so dependency PRs could enter a merge queue: a required queue rejects Renovate's direct API merge. The queue is not being enabled. The daily pricing workflow pushes straight to main with the Actions token, and GitHub rejects the GitHub Actions integration as a ruleset bypass actor (422), so a queue ruleset would block that push.
Without a queue or required checks, GitHub auto-merge adds nothing over Renovate's own automerge, so this restores platformAutomerge: false. The merge_group triggers from #2062 stay; they are inert until a queue exists.
Summary by cubic
Restores Renovate's platformAutomerge to false since the GitHub auto-merge from #2062 depends on a merge queue that isn't being enabled: adding a queue ruleset would block the daily pricing workflow's direct push to main with the Actions token. Without a queue or required checks, GitHub auto-merge adds nothing over Renovate's own automerge. The merge_group triggers remain but are inert.
Written for commit 69f4603. Summary will update on new commits.
Summary by CodeRabbit
Chores
Dependency update pull requests will no longer be merged automatically by the hosting platform. Updates will require a separate merge step.
#2062 switched Renovate to GitHub auto-merge so dependency PRs could enter a
merge queue, since a required queue rejects Renovate's direct API merge. The
queue is not being enabled: the daily pricing workflow pushes straight to main
with the Actions token, and a ruleset cannot list the GitHub Actions integration
as a bypass actor. Without a queue or required checks, GitHub auto-merge adds
nothing over Renovate's own automerge, so restore the previous setting.
ccusage/ccusage#2062: Changes the same Renovate setting to true for a merge-queue setup. This PR changes it back to false.
Merge Risk: Minimal · up to 69f46
Renovate will use its own automerge behavior. No merge-blocking issue is evident.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly summarizes the main change: turning Renovate’s platform automerge off.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: a2e3e661-2750-478c-af20-d061005baa53
Commits
Reviewing files that changed from the base of the PR and between 10fcd94 and 69f4603.
Files selected for processing: 1
.github/renovate.json
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review.
The reason will be displayed to describe this comment to others. Learn more.
✅ No new issues found.
Single-line revert is correct and safe to merge.
Reviewed changes in this run:
Restore Renovate self-automerge — flips platformAutomerge back to false in .github/renovate.json, returning to Renovate merging via its own API instead of GitHub auto-merge.
The reasoning in the PR description holds up: #2062 enabled GitHub auto-merge in anticipation of a merge queue, the queue is not being enabled, and a queue ruleset would block the daily pricing workflow's direct push to main. The merge_group triggers from #2062 stay and are inert without a queue, so this revert cleanly restores the prior known-good behavior with no other effect.
This compares the PR package against the configured base package on the same CI runner.
Package runtime diagnostics
Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.
Fixtures: Claude /home/runner/_work/_temp/ccusage-large-fixture (1.01 GiB, 2597 files), Codex /home/runner/_work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.
Command
Runtime
Input
Median
Throughput
Samples
claude --offline --json
Package wrapper
1.01 GiB
337.5ms
2.98 GiB/s
1
claude --offline --json
Installed native binary
1.01 GiB
305.3ms
3.30 GiB/s
1
codex --offline --json
Package wrapper
1.01 GiB
187.3ms
5.37 GiB/s
1
codex --offline --json
Installed native binary
1.01 GiB
153.4ms
6.56 GiB/s
1
Committed fixture performance
Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.
Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.
Command
Input
Base median
PR median
PR vs base
Base peak RSS
PR peak RSS
PR/base RSS
Base throughput
PR throughput
claude daily --offline --json
0.00 MiB
43.7ms
43.9ms
1.00x
56.00 MiB
55.75 MiB
1.00x
0.04 MiB/s
0.04 MiB/s
claude session --offline --json
0.00 MiB
43.0ms
43.4ms
0.99x
56.00 MiB
55.75 MiB
1.00x
0.04 MiB/s
0.04 MiB/s
codex daily --offline --json
0.00 MiB
43.7ms
43.2ms
1.01x
55.75 MiB
55.50 MiB
1.00x
0.02 MiB/s
0.02 MiB/s
codex session --offline --json
0.00 MiB
40.9ms
42.4ms
0.97x
55.75 MiB
56.00 MiB
1.00x
0.02 MiB/s
0.02 MiB/s
Large real-world-shaped fixture performance
Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.
Fixtures: Claude /home/runner/_work/_temp/ccusage-large-fixture (1.01 GiB, 2597 files), Codex /home/runner/_work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.
Command
Input
Base median
PR median
PR vs base
Base peak RSS
PR peak RSS
PR/base RSS
Base throughput
PR throughput
claude --offline --json
1.01 GiB
317.0ms
352.6ms
0.90x
891.35 MiB
903.34 MiB
1.01x
3.18 GiB/s
2.86 GiB/s
codex --offline --json
1.01 GiB
187.4ms
194.0ms
0.97x
695.73 MiB
699.73 MiB
1.01x
5.37 GiB/s
5.19 GiB/s
Artifact size
Artifact
Base
PR
Delta
Ratio
packed ccusage-*.tgz
27.66 KiB
27.67 KiB
+0.00 KiB
1.00x
installed native package binary
4974.97 KiB
4974.97 KiB
+0.00 KiB
1.00x
Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.
This compares the Rust PR release binary against the configured base package on the same CI runner.
Package runtime diagnostics
Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.
Fixtures: Claude /home/runner/_work/_temp/ccusage-large-fixture (1.01 GiB, 2597 files), Codex /home/runner/_work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.
Command
Runtime
Input
Median
Throughput
Samples
claude --offline --json
Package wrapper
1.01 GiB
507.5ms
1.98 GiB/s
1
claude --offline --json
Installed native binary
1.01 GiB
475.2ms
2.12 GiB/s
1
codex --offline --json
Package wrapper
1.01 GiB
259.2ms
3.88 GiB/s
1
codex --offline --json
Installed native binary
1.01 GiB
224.5ms
4.48 GiB/s
1
Committed fixture performance
Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.
Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published native ccusage binary from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.
Command
Input
Base median
PR median
PR vs base
Base peak RSS
PR peak RSS
PR/base RSS
Base throughput
PR throughput
claude daily --offline --json
0.00 MiB
42.0ms
18.4ms
2.28x
55.50 MiB
23.22 MiB
0.42x
0.04 MiB/s
0.08 MiB/s
claude session --offline --json
0.00 MiB
38.9ms
22.6ms
1.72x
56.00 MiB
23.22 MiB
0.41x
0.04 MiB/s
0.07 MiB/s
codex daily --offline --json
0.00 MiB
42.1ms
15.9ms
2.65x
55.75 MiB
27.22 MiB
0.49x
0.02 MiB/s
0.05 MiB/s
codex session --offline --json
0.00 MiB
39.4ms
15.9ms
2.47x
55.75 MiB
27.22 MiB
0.49x
0.02 MiB/s
0.05 MiB/s
Large real-world-shaped fixture performance
Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.
Fixtures: Claude /home/runner/_work/_temp/ccusage-large-fixture (1.01 GiB, 2597 files), Codex /home/runner/_work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published native ccusage binary from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.
Command
Input
Base median
PR median
PR vs base
Base peak RSS
PR peak RSS
PR/base RSS
Base throughput
PR throughput
claude --offline --json
1.01 GiB
349.8ms
700.7ms
0.50x
881.34 MiB
909.34 MiB
1.03x
2.88 GiB/s
1.44 GiB/s
codex --offline --json
1.01 GiB
277.5ms
219.5ms
1.26x
671.73 MiB
649.71 MiB
0.97x
3.63 GiB/s
4.59 GiB/s
Artifact size
Artifact
Base
PR
Delta
Ratio
packed ccusage-*.tgz
27.66 KiB
27.67 KiB
+0.00 KiB
1.00x
installed native package binary
4974.97 KiB
4974.97 KiB
+0.00 KiB
1.00x
Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
![pullfrog[bot]](https://avatars.githubusercontent.com/in/1768019?s=60&v=4){kind=small}
#2062 switched Renovate to GitHub auto-merge so dependency PRs could enter a merge queue: a required queue rejects Renovate's direct API merge. The queue is not being enabled. The daily pricing workflow pushes straight to
mainwith the Actions token, and GitHub rejects the GitHub Actions integration as a ruleset bypass actor (422), so a queue ruleset would block that push.Without a queue or required checks, GitHub auto-merge adds nothing over Renovate's own automerge, so this restores
platformAutomerge: false. Themerge_grouptriggers from #2062 stay; they are inert until a queue exists.Summary by cubic
Restores Renovate's
platformAutomergetofalsesince the GitHub auto-merge from #2062 depends on a merge queue that isn't being enabled: adding a queue ruleset would block the daily pricing workflow's direct push tomainwith the Actions token. Without a queue or required checks, GitHub auto-merge adds nothing over Renovate's own automerge. Themerge_grouptriggers remain but are inert.Written for commit 69f4603. Summary will update on new commits.
Summary by CodeRabbit