ci(nix-cachix-setup): parameterize gc-max-store-size-linux#231
ci(nix-cachix-setup): parameterize gc-max-store-size-linux#231thedavidmeister wants to merge 6 commits into
Conversation
The composite hardcoded the cache-nix-action linux GC budget at 8G, so a consumer with a smaller (docs/subgraph) or larger (webapp) build could not reuse the composite without re-running cache-nix-action itself and re-pinning that action inline. Expose `gc-max-store-size-linux` (default 8G, unchanged behavior) alongside the existing `gc-max-store-size-macos` input so callers pass their own budget and the cache-nix-action SHA stays single-sourced here. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 19 minutes and 45 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ze-gc-max-store-size-linux
What
Expose a
gc-max-store-size-linuxinput on thenix-cachix-setupcomposite action (default8G, unchanged behavior), alongside the existinggc-max-store-size-macosinput. The bundledcache-nix-actionstep now reads it instead of a hardcoded8G.Why
The composite is the single source of truth for the pinned third-party action SHAs (
nixbuild/nix-quick-install-action,cachix/cachix-action,nix-community/cache-nix-action). It hardcoded the linux GC budget at8G. A downstream consumer whose build wants a different budget — a small docs/subgraph build (1G) or a larger webapp build (10G) — could not reuse the composite without settingcache-nix: falseand runningcache-nix-actionitself, which re-introduces an inline pin of that action in the consumer and defeats single-sourcing.This unblocks rainlanguage/raindex#2724: raindex is converting its 14 workflows to consume these composites (inheriting the pins) instead of inline-pinning the shared actions, and several of those workflows need a non-
8Gbudget.Behavior
Default
8Gkeeps every current caller identical. Only callers that pass the new input change.🤖 Generated with Claude Code