Skip to content

chore(deps): update pullfrog/pullfrog action to v0.1.119 - #2049

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/pullfrog-pullfrog-0.x
Nov 9, 2026
Merged

renovate[bot] merged 1 commit into
mainfrom
renovate/pullfrog-pullfrog-0.x

Conversation

@renovate

@renovate renovate Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Pending
pullfrog/pullfrog action patch v0.1.118 → v0.1.119 v0.1.124 (+4)

Release Notes

pullfrog/pullfrog

v0.1.119

Compare Source

This release fixes a startup failure on self-hosted runners that share git objects and a false failure on Review runs started from an issue.

Fixes
Area What changed Link
Self-hosted runners Runners that share objects through GIT_ALTERNATE_OBJECT_DIRECTORIES no longer fail at startup with fatal: bad object HEAD, and PR checkout works on them again. Shell commands can now see that one variable 2f48b16
Review runs on an issue A run that delivered its result in a comment no longer fails with Review mode finished without calling create_pull_request_review. A run on a pull request is still held to submitting a review 7f93002
Reviews requested from an issue When the run reviews a pull request the issue named, the issue's progress comment now links to the review. It used to be deleted 7f93002
codenav With codenav on, a symbol a few lines off the given line now resolves to the nearest lines that have it, up to 10 lines either side. It used to exit 2 a8ad804

Full Changelog: pullfrog/pullfrog@v0.1.118...v0.1.119


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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@coderabbitai

coderabbitai Bot commented Nov 9, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

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

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 683e442c-4626-4bd2-80a8-0f82dbd13743

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
  • 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.

Share

@pkg-pr-new

pkg-pr-new Bot commented Nov 9, 2026

Copy link
Copy Markdown

Open in StackBlitz

ccusage

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

@ccusage/ccusage-darwin-arm64

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

@ccusage/ccusage-darwin-x64

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

@ccusage/ccusage-linux-arm64

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

@ccusage/ccusage-linux-x64

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

@ccusage/ccusage-win32-x64

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

commit: ab22c9c

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: ab22c9c15ab5
Base SHA: 22481062aee5

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 491.1ms 2.05 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 429.5ms 2.34 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 206.8ms 4.87 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 172.7ms 5.83 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 61.8ms 58.6ms 1.05x 56.00 MiB 55.75 MiB 1.00x 0.03 MiB/s 0.03 MiB/s
claude session --offline --json 0.00 MiB 57.9ms 52.9ms 1.09x 55.75 MiB 55.75 MiB 1.00x 0.03 MiB/s 0.03 MiB/s
codex daily --offline --json 0.00 MiB 55.3ms 56.0ms 0.99x 56.00 MiB 55.50 MiB 0.99x 0.02 MiB/s 0.02 MiB/s
codex session --offline --json 0.00 MiB 56.8ms 53.1ms 1.07x 56.00 MiB 55.75 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 485.8ms 499.0ms 0.97x 931.09 MiB 917.10 MiB 0.98x 2.07 GiB/s 2.02 GiB/s
codex --offline --json 1.01 GiB 214.5ms 217.1ms 0.99x 495.43 MiB 507.43 MiB 1.02x 4.69 GiB/s 4.64 GiB/s

Artifact size

Artifact Base PR Delta Ratio
packed ccusage-*.tgz 27.67 KiB 27.66 KiB -0.00 KiB 1.00x
installed native package binary 4994.97 KiB 4994.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.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: ab22c9c15ab5
Base SHA: 22481062aee5

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 532.3ms 1.89 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 454.8ms 2.21 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 215.2ms 4.68 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 191.9ms 5.25 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 54.8ms 19.6ms 2.80x 55.50 MiB 22.97 MiB 0.41x 0.03 MiB/s 0.08 MiB/s
claude session --offline --json 0.00 MiB 55.0ms 21.3ms 2.58x 55.50 MiB 22.97 MiB 0.41x 0.03 MiB/s 0.07 MiB/s
codex daily --offline --json 0.00 MiB 51.0ms 22.8ms 2.24x 55.75 MiB 26.97 MiB 0.48x 0.02 MiB/s 0.04 MiB/s
codex session --offline --json 0.00 MiB 61.7ms 21.5ms 2.87x 56.00 MiB 26.97 MiB 0.48x 0.01 MiB/s 0.04 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 561.4ms 449.3ms 1.25x 927.34 MiB 905.08 MiB 0.98x 1.79 GiB/s 2.24 GiB/s
codex --offline --json 1.01 GiB 222.5ms 179.8ms 1.24x 481.44 MiB 513.44 MiB 1.07x 4.52 GiB/s 5.60 GiB/s

Artifact size

Artifact Base PR Delta Ratio
packed ccusage-*.tgz 27.67 KiB 27.66 KiB -0.00 KiB 1.00x
installed native package binary 4994.97 KiB 4994.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.

@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 ab22c9c Commit Preview URL

Branch Preview URL
Nov 09 2026, 07:12 PM

@renovate
renovate Bot merged commit 5d9fc22 into main Nov 9, 2026
55 checks passed
@renovate
renovate Bot deleted the renovate/pullfrog-pullfrog-0.x branch November 9, 2026 19:47
@github-actions github-actions Bot mentioned this pull request Nov 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.

0 participants