Repository navigation
docs: say micropython-pydevices pins the LVGL commit, not which file - #17
Merged
Merged
Conversation
micropython-pydevices is moving its pins into one DEPENDENCIES.lock, so the guides no longer name modules.lock.
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 two firmware guides said
build_mp.pyfetches omnipython-lvgl at the commit micropython-pydevices'modules.lockpins. That file is going away: micropython-pydevices is moving its pins into oneDEPENDENCIES.lock.The guides now say micropython-pydevices pins the commit, without naming the file, so they read right before and after that change.
Only the wording of two sentences changes. No build or code reads these pages.