Skip to content

chore(deps): lock file maintenance - #1800

Merged
ryoppippi merged 4 commits into
mainfrom
renovate/lock-file-maintenance
Oct 9, 2026
Merged

ryoppippi merged 4 commits into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

CI repair

The refreshed Bun lockfiles use version 2, which released bun2nix 2.1.2 rejects. This now pins the tested compatibility commit from bun2nix PR #110 and freezes that input in Renovate until the fix is released. The refreshed dependencies are retained, and the matching changelogithub/bun.nix artifact has been regenerated.

Validation: just gen-bun-nix, formatting, the Nix Bun artifact consistency check, the Nix changelogithub package build, and applicable commit/push hooks passed on macOS arm64. GitHub CI validates the final commit.

@coderabbitai

coderabbitai Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 5951e7d8-1fcf-41a0-a630-7cd8dce1f9f3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


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.

@socket-security

socket-security Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​@​types/​node@​24.19.01001008196100
Updatedcargo/​smallvec@​1.16.1 ⏵ 1.16.210010093100100
Updatedcargo/​sqlite@​0.37.0 ⏵ 0.37.310010093100100

View full report

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 25, 2026 •

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 238831d Commit Preview URL

Branch Preview URL
Oct 02 2026, 07:29 PM

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 22 times, most recently from 2af989c to be40bf4 Compare September 29, 2026 19:08
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 9 times, most recently from 69b9b52 to 246f8b1 Compare October 2, 2026 13:57
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 246f8b1 to 42e1edc Compare October 2, 2026 18:08
@renovate

renovate Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@pkg-pr-new

pkg-pr-new Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

ccusage

npx https://pkg.pr.new/ccusage@1800

@ccusage/ccusage-darwin-arm64

npx https://pkg.pr.new/@ccusage/ccusage-darwin-arm64@1800

@ccusage/ccusage-darwin-x64

npx https://pkg.pr.new/@ccusage/ccusage-darwin-x64@1800

@ccusage/ccusage-linux-arm64

npx https://pkg.pr.new/@ccusage/ccusage-linux-arm64@1800

@ccusage/ccusage-linux-x64

npx https://pkg.pr.new/@ccusage/ccusage-linux-x64@1800

@ccusage/ccusage-win32-x64

npx https://pkg.pr.new/@ccusage/ccusage-win32-x64@1800

commit: 238831d

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 5ad8bf9e089c
Base SHA: 065e09981839

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 392.6ms 2.56 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 433.9ms 2.32 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 184.1ms 5.47 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 146.5ms 6.87 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 41.1ms 17.6ms 2.33x 57.00 MiB 22.96 MiB 0.40x 0.04 MiB/s 0.09 MiB/s
claude session --offline --json 0.00 MiB 44.8ms 11.6ms 3.87x 57.00 MiB 22.96 MiB 0.40x 0.03 MiB/s 0.13 MiB/s
codex daily --offline --json 0.00 MiB 40.7ms 12.7ms 3.21x 57.00 MiB 22.95 MiB 0.40x 0.02 MiB/s 0.07 MiB/s
codex session --offline --json 0.00 MiB 40.6ms 10.8ms 3.77x 57.25 MiB 22.96 MiB 0.40x 0.02 MiB/s 0.08 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 406.0ms 380.3ms 1.07x 933.09 MiB 929.09 MiB 1.00x 2.48 GiB/s 2.65 GiB/s
codex --offline --json 1.01 GiB 154.9ms 122.4ms 1.27x 441.41 MiB 443.41 MiB 1.00x 6.50 GiB/s 8.22 GiB/s

Artifact size

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

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 5ad8bf9e089c
Base SHA: 065e09981839

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 346.8ms 2.90 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 300.4ms 3.35 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 145.3ms 6.93 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 117.7ms 8.55 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.0ms 41.7ms 1.03x 57.50 MiB 56.75 MiB 0.99x 0.04 MiB/s 0.04 MiB/s
claude session --offline --json 0.00 MiB 43.7ms 41.5ms 1.05x 57.00 MiB 56.75 MiB 1.00x 0.04 MiB/s 0.04 MiB/s
codex daily --offline --json 0.00 MiB 40.2ms 39.5ms 1.02x 57.25 MiB 56.50 MiB 0.99x 0.02 MiB/s 0.02 MiB/s
codex session --offline --json 0.00 MiB 39.5ms 37.7ms 1.05x 56.75 MiB 57.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 362.4ms 356.7ms 1.02x 915.08 MiB 897.07 MiB 0.98x 2.78 GiB/s 2.82 GiB/s
codex --offline --json 1.01 GiB 138.9ms 140.3ms 0.99x 443.42 MiB 451.41 MiB 1.02x 7.25 GiB/s 7.18 GiB/s

Artifact size

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

The refreshed Bun lockfiles use version 2, but released bun2nix only
accepts version 1. Pin the tested upstream compatibility fix until it
is released and prevent Renovate from moving back to the incompatible
generator.

Regenerate the committed Nix dependency artifacts while retaining the
lockfile maintenance updates.
@ryoppippi

Copy link
Copy Markdown
Member

@coderabbitai @cubic-dev-ai Please review the latest CI repair. The lockfile maintenance updated Bun lockfiles beyond the format supported by released bun2nix. This pins upstream's tested compatibility fix and regenerates the Nix dependency artifacts while preserving the refreshed dependencies. The pin stays fixed in Renovate until a compatible release is available.

@cubic-dev-ai

cubic-dev-ai Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

@coderabbitai @cubic-dev-ai Please review the latest CI repair. The lockfile maintenance updated Bun lockfiles beyond the format supported by released bun2nix. This pins upstream's tested compatibility fix and regenerates the Nix dependency artifacts while preserving the refreshed dependencies. The pin stays fixed in Renovate until a compatible release is available.

@ryoppippi Couldn't start the review: please upgrade to a paid plan to review bot-authored PRs.

@coderabbitai

coderabbitai Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

@ryoppippi I’ll review the latest CI repair, focusing on:

  • The bun2nix compatibility commit and its locked revision.
  • The Renovate rule that keeps the pin fixed.
  • The regenerated Nix artifacts and preservation of refreshed dependencies.
  • The CI results for the latest commit.

Thanks for explaining why the pin must remain fixed.


✏️ Learnings added
Learnt from: ryoppippi
URL: https://github.com/ccusage/ccusage/pull/1800

Timestamp: 2026-10-02T19:21:43.436Z
Learning: In ccusage/ccusage, the bun2nix compatibility pin introduced in PR #1800 is intentional: refreshed version-2 Bun lockfiles are unsupported by released bun2nix 2.1.2. The project pins the tested compatibility commit from nix-community/bun2nix PR #110 and freezes that input in Renovate until a compatible release is available. Preserve the refreshed dependencies when evaluating this repair.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

⚠️ Action not completed

Review skipped.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 238831d2bb75
Base SHA: 01bea67492aa

Performance comparison skipped.

Base package URL was not ready before 300.000s. Fixture performance comparison requires a base package when --base-dir is not provided.

Base package: 01bea67492aa

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 238831d2bb75
Base SHA: 01bea67492aa

Performance comparison skipped.

Base package URL was not ready before 300.000s. Fixture performance comparison requires a base package when --base-dir is not provided.

Base package: 01bea67492aa

@ryoppippi
ryoppippi merged commit dba346c into main Oct 9, 2026
36 checks passed
@ryoppippi
ryoppippi deleted the renovate/lock-file-maintenance branch October 9, 2026 22:15
@github-actions github-actions Bot mentioned this pull request Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant