Repository navigation
docs(packages): explain updates from the compatible collection - #70
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.
The command guide still says Official Package Sources cannot be updated. The CLI now supports those updates through the tag matching the checkout's Package API.
Correct the install and update instructions, command table, and examples. Keep the Core guide and the CLI guide consistent. Follow-up to #66 and #69 for LyraCoreProject/LyraCore#636.
Checked the text against
official.rs,git.rs, and Package discovery. Documentation only;git diff --checkpasses. Independent Standards and adversarial Spec reviews cleared final commit98cf4be, including the explanation that disabled Packages stay excluded from compilation during preflight.Implemented with GPT-6 Astra in the Codex harness through T3 Code.