Release v1.8.1 Lilu compatibility fix - #6
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.
What changed
Why
Lilu 1.7.0 systems were rejected by the bundle dependency before PC711Probe could load, even though every imported Lilu API used by the project is already present with the same ABI in Lilu 1.6.1.
Compatibility impact
No runtime patch, SSD matcher, Darwin range, or target class changed. The standard build remains limited to PCI ID 1C5C:174A plus NVMe class validation; the Force build remains the explicit opt-in for other NVMe PCI IDs.
Validation
./Scripts/verify.shgit diff --check