Skip to content

chore(renovate): ask for full mode from the repository config - #1516

Merged
ryoppippi merged 1 commit into
mainfrom
chore/renovate-mode-full
Jul 28, 2026
Merged

ryoppippi merged 1 commit into
mainfrom
chore/renovate-mode-full

Conversation

@ryoppippi

@ryoppippi ryoppippi commented Jul 28, 2026 •

Copy link
Copy Markdown
Member

Summary

The Mend dashboard explains the five weeks of silence, and it is not what any of the earlier guesses said. On https://developer.mend.io/github/ccusage:

Default Engine Settings
  Dependency Updates (Renovate): Silent
  Renovate plan: Community (Free)

Installed Repositories
  ccusage | Renovate: Enabled | Status: activated | Last Job Run: 1 hours ago

The repository is enabled and activated, and its job list shows runs completing every few hours (DONE), including webhook-triggered ones from today's merges. But the org's default engine setting is Silent, and in silent mode renovate does all the work and then creates no branches, pull requests or issues. That matches everything observed: a config that validates, a local --dry-run=full that finds 26 pending updates, and nothing ever appearing on the repo.

What Changed

Sets "mode": "full" in .github/renovate.json.

mode is not a global-only option, so a repository config is allowed to set it (verified: the validator raises no global-option warning for it in a repo config). If the platform applies silent as an org default, this overrides it. If it applies it as forced config, only the dashboard toggle helps and this line is inert but harmless.

The reliable fix is still flipping Dependency Updates off Silent in the Mend org settings; this is the half that can live in the repo.

Testing

renovate-config-validator --strict passes.


View with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled.


Summary by cubic

Switches Renovate to full mode by adding "mode": "full" in .github/renovate.json, so it will open update branches and PRs instead of running silently. If Silent is enforced at the org level, this is a safe no-op.

Written for commit 3f0655a. Summary will update on new commits.

Review in cubic

Summary by CodeRabbit

  • Chores
    • Updated automated dependency maintenance configuration to use its full operating mode.

The Mend dashboard explains the silence: the ccusage org's Default Engine
Settings have `Dependency Updates (Renovate): Silent`, while the repository
row itself reads Enabled/activated with jobs completing every few hours. In
silent mode renovate does all the work and then creates no branches, pull
requests or issues, which is exactly what we saw - a config that validates, a
local dry-run that finds 26 updates, and nothing ever appearing.

`mode` is not a global-only option, so a repository config may set it. If the
platform applies silent as an org default, this overrides it; if it applies it
as forced config, only the dashboard toggle will help and this line is inert.
Copilot AI review requested due to automatic review settings July 28, 2026 11:42

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@coderabbitai

coderabbitai Bot commented Jul 28, 2026 •

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 59aa403a-67d9-4ab6-926f-7bb2b8dcd32c

📥 Commits

Reviewing files that changed from the base of the PR and between cc5be7d and 3f0655a.

📒 Files selected for processing (1)
  • .github/renovate.json

📝 Walkthrough

Walkthrough

Renovate configuration is updated to explicitly set its operating mode to full; all other documented settings remain unchanged.

Changes

Renovate configuration

Layer / File(s) Summary
Set Renovate full mode
.github/renovate.json
Adds "mode": "full" to the Renovate configuration.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: copilot

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the change: updating Renovate repository config to use full mode.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/renovate-mode-full

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
ccusage-guide 3f0655a Commit Preview URL

Branch Preview URL
Jul 28 2026, 11:43 AM

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes — adds "mode": "full" to .github/renovate.json so Renovate creates branches and PRs instead of running silently under the Mend org's default "Silent" engine setting.

  • Enable mode: "full" in Renovate repo config — overrides the org-level Silent default so dependency updates appear as PRs. Inert but harmless if Mend enforces Silent at the platform level rather than as a default.

Pullfrog  | ⚠️ this action is pinned to a commit SHA, which freezes the cleanup step — switch to @v0 or keep the SHA fresh with Dependabot | View workflow run | Using DeepSeek Pro (free via Pullfrog for OSS) | 𝕏

@ryoppippi
ryoppippi merged commit b16676f into main Jul 28, 2026
23 checks passed
@ryoppippi
ryoppippi deleted the chore/renovate-mode-full branch July 28, 2026 11:45
@github-actions

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 3f0655aa1fe5
Base SHA: cc5be7d68001

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 342.2ms 2.94 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 318.9ms 3.16 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 134.2ms 7.50 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 112.7ms 8.94 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 28.7ms 26.4ms 1.09x 55.00 MiB 55.25 MiB 1.00x 0.05 MiB/s 0.06 MiB/s
claude session --offline --json 0.00 MiB 25.6ms 24.2ms 1.06x 55.00 MiB 55.00 MiB 1.00x 0.06 MiB/s 0.06 MiB/s
codex daily --offline --json 0.00 MiB 25.0ms 25.6ms 0.98x 55.00 MiB 55.00 MiB 1.00x 0.03 MiB/s 0.03 MiB/s
codex session --offline --json 0.00 MiB 23.3ms 25.6ms 0.91x 55.00 MiB 54.75 MiB 1.00x 0.04 MiB/s 0.03 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 371.0ms 358.4ms 1.04x 942.58 MiB 960.58 MiB 1.02x 2.71 GiB/s 2.81 GiB/s
codex --offline --json 1.01 GiB 117.8ms 121.5ms 0.97x 414.65 MiB 408.64 MiB 0.99x 8.55 GiB/s 8.28 GiB/s

Artifact size

Artifact Base PR Delta Ratio
packed ccusage-*.tgz 18.78 KiB 18.78 KiB +0.00 KiB 1.00x
installed native package binary 4156.78 KiB 4156.78 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.

@github-actions

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 3f0655aa1fe5
Base SHA: cc5be7d68001

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 353.4ms 2.85 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 321.5ms 3.13 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 134.7ms 7.47 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 122.7ms 8.20 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 29.4ms 5.4ms 5.45x 55.25 MiB 12.44 MiB 0.23x 0.05 MiB/s 0.29 MiB/s
claude session --offline --json 0.00 MiB 27.4ms 2.8ms 9.79x 55.00 MiB 12.45 MiB 0.23x 0.06 MiB/s 0.55 MiB/s
codex daily --offline --json 0.00 MiB 26.5ms 2.5ms 10.74x 55.00 MiB 10.44 MiB 0.19x 0.03 MiB/s 0.35 MiB/s
codex session --offline --json 0.00 MiB 25.6ms 2.5ms 10.17x 55.00 MiB 10.44 MiB 0.19x 0.03 MiB/s 0.34 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 397.4ms 336.6ms 1.18x 956.57 MiB 938.57 MiB 0.98x 2.53 GiB/s 2.99 GiB/s
codex --offline --json 1.01 GiB 124.4ms 98.3ms 1.26x 424.90 MiB 428.64 MiB 1.01x 8.10 GiB/s 10.24 GiB/s

Artifact size

Artifact Base PR Delta Ratio
packed ccusage-*.tgz 18.78 KiB 18.78 KiB +0.00 KiB 1.00x
installed native package binary 4156.78 KiB 4156.78 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.

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.

2 participants