Repository navigation
fix: support upstream per-board battery configuration - #20
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.
Update
rmk-configandrynk-kletogether from5f06e5bfto6e84c364, with the corresponding lockfile entries. This lets rmkit parse RMK's new per-board battery tables instead of rejecting the nRF52840 BLE unibody and split configs withunknown field battery.Validation: all 14 existing tests pass; formatting, Clippy, build, and bundled-config smoke checks pass. The upstream drift checker exits successfully with all 26 example configs parsed.
Closes #19.