Skip to content

fix(nix): pin models-dev-gen remeda to models.dev's version and stop Renovate drift - #1915

Merged
ryoppippi merged 2 commits into
mainfrom
cursor/pin-models-dev-gen-remeda-ea27
Oct 18, 2026
Merged

ryoppippi merged 2 commits into
mainfrom
cursor/pin-models-dev-gen-remeda-ea27

Conversation

@ryoppippi

@ryoppippi ryoppippi commented Oct 18, 2026 •

Copy link
Copy Markdown
Member

Summary

Open in Web Open in Cursor 

Summary by cubic

Fixes models-dev-gen dependency drift by pinning remeda back to the version models.dev's bun.lock uses, and teaches Renovate to leave those dependencies alone.

  • Reverts remeda to 2.33.7 in nix/tools/models-dev-gen and regenerates bun.lock and bun.nix to match.
  • Disables Renovate updates for remeda and zod in that package so they stay aligned with the pinned models-dev input.
  • Marks autofix.ci commits as generated so Renovate keeps automerging its lockfile regeneration PRs.

Written for commit cfb7ef3. Summary will update on new commits.

View guided diff Turn on auto-fix

Summary by CodeRabbit

  • Chores
    • Updated dependency management to ignore commits from the designated automated maintenance bot.
    • Pinned Remeda to version 2.33.7 and disabled automated updates for Remeda and Zod in the affected development tool.
    • No end-user-facing feature changes are included in this update.

@coderabbitai

coderabbitai Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

⛔ Files ignored due to path filters: 1
  • nix/tools/models-dev-gen/bun.lock is excluded by !**/*.lock
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 5f4dc222-607a-4b61-b0a1-b11f55936104
📥 Commits

Reviewing files that changed from the base of the PR and between 2d1bcf7 and cfb7ef3.

⛔ Files ignored due to path filters: 1
  • nix/tools/models-dev-gen/bun.lock is excluded by !**/*.lock

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

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f792f671-968d-4a97-9fdb-23aaf7578d10
📥 Commits

Reviewing files that changed from the base of the PR and between 6039ff6 and 2d1bcf7.

⛔ Files ignored due to path filters: 1
  • nix/tools/models-dev-gen/bun.lock is excluded by !**/*.lock
📒 Files selected for processing: 3
  • .github/renovate.json
  • nix/tools/models-dev-gen/bun.nix
  • nix/tools/models-dev-gen/package.json

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

📝 Walkthrough

The models-dev-gen package pins remeda to version 2.33.7. Renovate configuration ignores commits from a specified CI bot and disables updates for remeda and zod in that package.

Changes: Remeda dependency and Renovate configuration

Layer / File(s) Summary
Pin remeda version
nix/tools/models-dev-gen/package.json, nix/tools/models-dev-gen/bun.nix
The package manifest and Nix package entry specify remeda version 2.33.7. The Nix entry uses the corresponding tarball URL and hash.
Configure Renovate rules
.github/renovate.json
Renovate ignores commits from the specified autofix CI bot and disables updates for remeda and zod in the models-dev-gen package.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 2d1bc

The dependency pin and Renovate rules match the intended package and bot behavior. No actionable merge-blocking risk remains.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly identifies the primary changes: pinning remeda for models-dev-gen and preventing Renovate drift. It is concise and specific.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 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.

❤️ Share

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

@socket-security

socket-security Bot commented Oct 18, 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
Updatednpm/​remeda@​2.51.0 ⏵ 2.33.7100 +110083 -196 -1100

View full report

@ryoppippi
ryoppippi marked this pull request as ready for review October 18, 2026 12:18
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 18, 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 cfb7ef3 Commit Preview URL

Branch Preview URL
Oct 18 2026, 12:36 PM

@cubic-dev-ai cubic-dev-ai 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 issues found across 4 files

View guided diff | Turn on auto-fix | Re-trigger cubic

@pkg-pr-new

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

Copy link
Copy Markdown

Open in StackBlitz

ccusage

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

@ccusage/ccusage-darwin-arm64

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

@ccusage/ccusage-darwin-x64

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

@ccusage/ccusage-linux-arm64

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

@ccusage/ccusage-linux-x64

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

@ccusage/ccusage-win32-x64

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

commit: cfb7ef3

@github-actions

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 2d1bcf7ca475
Base SHA: 6039ff67161a

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: 6039ff67161a

@github-actions

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: 2d1bcf7ca475
Base SHA: 6039ff67161a

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: 6039ff67161a

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

Important

Please rebase onto current main and regenerate the pricing snapshot under the pinned toolchain before merging. Details below.

Reviewed changes — reviewed all 27 commits in this PR against main:

  • Pin remeda to 2.33.7 — downgrades nix/tools/models-dev-gen/package.json from 2.51.0 with regenerated bun.lock and bun.nix.
  • Disable Renovate for remeda/zod — new packageRules entry scoped to nix/tools/models-dev-gen/package.json with enabled: false.
  • Ignore autofix-ci[bot] commits — adds gitIgnoredAuthors so Renovate keeps automerging its own lockfile PRs.
  • Bundled automation churn — flake.lock input bumps plus models-dev-pricing.json and models-dev-catalog-rules.json snapshot updates from 25 automation commits on this branch.

⚠️ Stale branch bundles superseded automation output

This branch forked from c1eb4489 but main has since moved forward with newer snapshots and a CI cadence change. Merging as-is would write stale flake.lock revs and an older models-dev-pricing.json over newer main data, silently reverting upstream pricing changes.

Technical details
# Stale base clobbers newer main

## Affected sites
- `flake.lock` — `litellm` and `models-dev` rev bumps already superseded on `main`
- `rust/crates/ccusage-core/src/models-dev-pricing.json` — snapshot older than `main` tip `b9efb84e`
- `rust/crates/ccusage-core/src/models-dev-catalog-rules.json` — same staleness risk

## Required outcome
- PR diff contains only the two fix commits (`2c2b3151`, `2d1bcf7c`) rebased onto current `main`; no automation commits unique to the branch.

⚠️ Snapshot was generated before the pin, not under it

The committed pricing snapshot predates the remeda downgrade commit, so it was produced with drifted remeda 2.51.0. The PR therefore does not yet prove the pinned 2.33.7 toolchain generates identical output, which is the whole point of the version alignment.

Technical details
# Snapshot not regenerated under pinned toolchain

## Affected sites
- `nix/tools/models-dev-gen/package.json:7` — pin to 2.33.7 landed after the snapshot commits
- `nix/tools/models-dev-gen/bun.lock:78` — same ordering issue
- `rust/crates/ccusage-core/src/models-dev-pricing.json` — needs a post-pin regeneration to confirm behavior-neutral

## Required outcome
- After rebasing, re-run `just gen-models-dev-pricing` under the pinned toolchain and commit the result, or confirm the output is byte-identical.

## Suggested approach
- Rebase first, then regenerate once, so the final snapshot reflects both the pin and the current `main` inputs.

Pullfrog  | Fix it ➔ | View workflow run | Using muse-spark-1.3-contributor (free via Pullfrog for OSS) | 𝕏

@cursor
cursor Bot force-pushed the cursor/pin-models-dev-gen-remeda-ea27 branch from 2d1bcf7 to cfb7ef3 Compare October 18, 2026 12:35

@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 — reviewed the delta since the prior pullfrog review (2d1bcf7c → cfb7ef3):

  • Rebased onto current main — dropped the 25 superseded automation commits so the diff is now exactly the 4 intended files.
  • Kept the remeda 2.51.0 → 2.33.7 pin with matching regenerated bun.lock and bun.nix hashes.
  • Kept the Renovate remeda/zod exclusion scoped to nix/tools/models-dev-gen/package.json.
  • Kept the gitIgnoredAuthors entry for autofix-ci[bot].

The stale-branch concern from the prior review is resolved by the rebase. The post-pin snapshot regeneration proof gap is carried as a non-blocking follow-up rather than re-raised here.

Pullfrog  | View workflow run | Using muse-spark-1.3-contributor (free via Pullfrog for OSS) | 𝕏

@github-actions

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: cfb7ef373eb0
Base SHA: b0904280a2c4

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 373.0ms 2.70 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 344.3ms 2.92 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 145.5ms 6.92 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 159.0ms 6.33 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.5ms 43.2ms 1.01x 55.50 MiB 55.75 MiB 1.00x 0.04 MiB/s 0.04 MiB/s
claude session --offline --json 0.00 MiB 36.9ms 43.1ms 0.86x 55.50 MiB 55.50 MiB 1.00x 0.04 MiB/s 0.04 MiB/s
codex daily --offline --json 0.00 MiB 38.5ms 37.6ms 1.03x 55.50 MiB 56.00 MiB 1.01x 0.02 MiB/s 0.02 MiB/s
codex session --offline --json 0.00 MiB 36.5ms 37.2ms 0.98x 55.50 MiB 55.50 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 361.4ms 378.6ms 0.95x 945.11 MiB 913.10 MiB 0.97x 2.79 GiB/s 2.66 GiB/s
codex --offline --json 1.01 GiB 152.9ms 140.1ms 1.09x 505.44 MiB 529.45 MiB 1.05x 6.58 GiB/s 7.19 GiB/s

Artifact size

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

Copy link
Copy Markdown
Contributor

ccusage performance comparison

PR SHA: cfb7ef373eb0
Base SHA: b0904280a2c4

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 395.1ms 2.55 GiB/s 1
claude --offline --json Installed native binary 1.01 GiB 371.5ms 2.71 GiB/s 1
codex --offline --json Package wrapper 1.01 GiB 139.6ms 7.21 GiB/s 1
codex --offline --json Installed native binary 1.01 GiB 107.6ms 9.36 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 46.5ms 14.7ms 3.17x 55.50 MiB 22.97 MiB 0.41x 0.03 MiB/s 0.11 MiB/s
claude session --offline --json 0.00 MiB 40.8ms 14.3ms 2.86x 55.75 MiB 22.97 MiB 0.41x 0.04 MiB/s 0.11 MiB/s
codex daily --offline --json 0.00 MiB 41.8ms 14.0ms 2.98x 55.50 MiB 29.22 MiB 0.53x 0.02 MiB/s 0.06 MiB/s
codex session --offline --json 0.00 MiB 38.8ms 14.2ms 2.73x 55.50 MiB 29.22 MiB 0.53x 0.02 MiB/s 0.06 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 426.4ms 383.8ms 1.11x 973.11 MiB 965.10 MiB 0.99x 2.36 GiB/s 2.62 GiB/s
codex --offline --json 1.01 GiB 135.3ms 114.2ms 1.19x 513.44 MiB 517.44 MiB 1.01x 7.44 GiB/s 8.82 GiB/s

Artifact size

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

@ryoppippi
ryoppippi merged commit 4dcf7f5 into main Oct 18, 2026
46 checks passed
@ryoppippi
ryoppippi deleted the cursor/pin-models-dev-gen-remeda-ea27 branch October 18, 2026 12:44
Buster210 added a commit to Buster210/ccusage that referenced this pull request Oct 20, 2026
Upstream tip: c76874e (2026-10-20, chore(pricing): update models.dev snapshot)
Previous fork base: 0c58b88 (the upstream commit this fork was synced to)

Synced 83 upstream commits on top of 0c58b88: 56 automated pricing
snapshot refreshes and the following meaningful ones:

  1cd29f5 chore(deps): update pnpm to v12.13.0 (ccusage#1907)
  e4f63ba chore(deps): update node.js to >=24.22.0 (ccusage#1908)
  130e502 ci: regenerate bun.nix automatically (ccusage#1909)
  259ec33 feat(adapter): report stored cost in JSON model breakdowns (ccusage#1903)
  c1eb448 chore: release v20.0.35 (ccusage#1901)
  2a0875f ci(pricing): update snapshots on push to main and daily instead of hourly (ccusage#1914)
  b090428 chore(deps): update github/codeql-action action to v4.39.0 (ccusage#1912)
  4dcf7f5 fix(nix): pin models-dev-gen remeda to models.dev's version and stop Renovate drift (ccusage#1915)
  46edb28 fix(nix): stop the dev shell from copying the whole repository (ccusage#1917)
  58ec8f1 fix(nix): let commits succeed in worktrees without a loaded dev shell (ccusage#1920)
  a570a6f fix(nix): vendor Cargo deps without import-from-derivation (ccusage#1918)
  f6d28c5 fix(antigravity): map model IDs 1418/1419 to gemini-4-argon (ccusage#1905)
  ce439e5 fix(antigravity): map model ID 1050 to gemini-3.1-flash-lite (ccusage#1902)
  e62a66f chore(deps): update pnpm to v12.14.0 (ccusage#1923)
  117ae68 ci(nix): make the macOS Nix cache save a trimmed store with the Crane layers (ccusage#1921)
  7a063a0 ci: shorten the Windows native build critical path (ccusage#1924)
  85ebca3 perf(rust): move pricing snapshots into a leaf crate (ccusage#1922)
  8fe3f47 perf(nix): build Crane layers with the binary's feature resolution (ccusage#1925)
  ac289aa perf(pricing): give the pricing refresh a verify-only TLS 1.3 rustls provider (ccusage#1927)
  d097f74 chore(deps): update rust crate rustls to 0.23.46 (ccusage#1928)
  f8aaf89 docs: use the compact pkg.pr.new URL for bunx previews [ci skip] (ccusage#1929)
  f56bb3d chore: release v20.0.36 (ccusage#1916)
  aaafb41 chore(deps): update dependency vitepress-plugin-group-icons to ^1.8.1 (ccusage#1931)
  0861e7f fix(claude): count requestless resp_ content blocks once (ccusage#1935)
  867c9f3 chore: release v20.0.37 (ccusage#1933)
  fa40bfd chore(deps): update songmu/tagpr action to v1.21.3 (ccusage#1937)
  de99d15 chore(deps): update rust crate zstd to 0.14.3 (ccusage#1936)

Fork wins kept: the SQLite on-disk cache with --live-only and the per-namespace
ledger, the pi adapter and its per-path namespaces, the OpenCode V2 loader, the
FxHash/Cow hot paths, the table renderer, clear-cache, and the tag-only release
workflow. Upstream's own release and tagpr machinery stays out.

Hand-resolved conflicts:

  rust/adapters/claude/src/lib.rs: upstream's resp_ message-id dedupe (ccusage#1935) lands
    beside the fork's requestless replay and collapse_replays rules.
  rust/adapters/claude/src/README.md: upstream's wording for the msg_/resp_ exception.
  rust/Cargo.toml: zstd 0.14.3, keeping the fork's exact `=` pin style.
  .github/workflows/release.yaml: the fork's tag-only release, without upstream's
    tagpr job or the songmu/tagpr action bump.
  apps/ccusage/package.json, docs/package.json, package.json: keep 20.0.34;
    upstream's 20.0.37 bump is dropped.
  packages/ccusage-*/package.json (6 files): stay deleted; the fork ships no npm
    wrapper packages and the release workflow does not read them.
  rust/adapters/claude/src/daily.rs: stays deleted; the fork's daily path lives in
    lib.rs and shares the dedupe helper the fix changes.

Fixes made while landing this sync, folded in so the merge stands green on its own:

  fix(ci): save the Nix store from the native build composites. The nested
    cache-nix-action read an empty primary-key at post-job and every native
    build failed; upstream's defer-save pattern is the fix.
  fix(rust): keep the agent-recorded cost for deleted sources. The recorded_cost
    ledger column carries it, so storedCost survives a deleted file. The ledger
    schema version stays at 2: the column is not a LedgerEntry field, so the blob
    layout is unchanged and the previously released binary keeps working.
  fix(rust): make the file fingerprint helper private, the one hawk finding. It is
    inherited from the pre-sync master, not introduced here.

Keep 20.0.34 numbering; DO NOT push a v20.0.34 tag from this fork (release.yaml
would publish fork bytes under upstream identity).
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