Repository navigation
chore: depend on bare LeviLamina in the client entry of lip.toml - #35
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
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 client entry now depends on bare
github.com/LiteLDev/LeviLaminainstead of#client: a lip.toml dependency is never rewritten, and the lip.toml releases of LeviLamina have noclientvariant.The range is
>26.60.6 <26.61.0instead of26.60.*, so it excludes every tooth.json release of LeviLamina, whose""variant is the server build. Until a lip.toml LeviLamina 26.60.7+ is released, a client install fails with "no version tag satisfies" instead of resolving to a server build. Server entries are unchanged.