Repository navigation
chore: update vendored submodules (libDaisy / DaisySP) - #11
Merged
Merged
Conversation
joak0068
approved these changes
Oct 11, 2026
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.
Automated weekly bump of the vendored libraries to their upstream default branch.
lib/libDaisy: facb66c7 -> 08087203lib/DaisySP: 599511b -> 2c72eafFirmware build with the updated libraries: success
(
success= compiles clean;failure= needs a compatibility fix before merging).Review the upstream changelogs, then merge if the build is green. The repo's
firmware.ymlCI does not run automatically on this bot PR (a GitHub limitationon
GITHUB_TOKEN-created PRs), which is why the build above runs inline.