Repository navigation
chore: no tracked Cargo.lock (no pins) - #92
Conversation
Decision (operator, 2026-10-16): no pins. The lock is removed from the tree and ignored so every build resolves the git-branch dependencies at their current heads instead of a frozen graph. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017SNHxJYC1MeW3HsyhGZo1E
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. 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 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
2 participants
Summary
Decision (operator, 2026-10-16): no pins. This removes the tracked
Cargo.lockfrom the tree and adds it to.gitignore, so every build resolves the git-branch dependencies at their current heads instead of a frozen graph. The same convention lance-graph, OGAR, HubSPO-rs and tesseract-rs already follow.Changes
git rm --cachedof every trackedCargo.lockin the repoCargo.lockappended to.gitignore(where it was not already listed)No source change. Local resolution: the next
cargo buildregenerates the lock from the latest heads.🤖 Generated with Claude Code
https://claude.ai/code/session_017SNHxJYC1MeW3HsyhGZo1E
Generated by Claude Code