Repository navigation
Describe Ledger's single, revision-named flake pin - #9
Merged
Merged
Conversation
Ledger dropped its lean/ submodule (ledger/ledger#3336): its flake input, whose URL names the revision, is now this repository's only pin there, and a development build opts in through LEDGER_LEAN_DIR. The downstream rule also ran backwards: main follows Ledger's pin, so a change is cut onto the pinned revision, lands with its C++ half, and main fast-forwards to it when Ledger's pull request merges. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cz3H32XazWJeNtvPbWHD6n
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ledger dropped its
lean/submodule in ledger/ledger#3336. Its flake input, whose URL names the revision, is now this repository's only pin there, and a development build opts in throughLEDGER_LEAN_DIR. README.md and AGENTS.md still described two pins.AGENTS.md also stated the downstream rule backwards. Main follows Ledger's pin, not the other way round: a change is cut onto the pinned revision, lands together with its C++ half, and main fast-forwards to it when Ledger's pull request merges. Squashing or rebasing a pinned commit would change the revision Ledger names.
This is a docs-only change; the oracle tree is unchanged. Merge it by fast-forwarding main to a41644b, not by squash or rebase, so the next pin-moving change can be cut on top of it.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Cz3H32XazWJeNtvPbWHD6n