Repository navigation
docs: use pinned Batter Git dependencies - #24
Merged
Merged
Conversation
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
1 participant
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.
Replace sibling-path installation examples in the README and relocation guide with copyable Git dependencies pinned to merged Batter commit
70cc6a05be6857aca6ea2f5f127258e75e673d8c. Remove the obsolete separate-repository consumer patch instructions. Update the README contract checker to require matching full Batter Git pins instead of sibling paths. Explain that related native and Batter packages should share one Git URL and revision.Follow-up to #23. The selected Batter revision contains both Runledger and Runlimit. No library code, manifests, lockfiles or database migrations change.
Validation: an isolated consumer using the exact README dependency block fetched the remote Git source, built and executed on Rust 1.94.0, and passed
cargo check --all-targets --locked, including the test-support dependency. Cargo metadata confirms all native and foundation packages use the same Git revision without sibling paths or consumer patches. TOML consistency, Markdown fences and whitespace checks passed. The repository README checker passes and rejected eight negative cases covering paths, registry dependencies, wrong repositories, short/branch/mixed revisions, missing packages and stale quick-start source blocks. Native Codex review of the complete pinned correction diff reported no findings.Owning task:
runledger-rj7.