Pinned the library submodules at the 6.5.2.202603 releases - #81
Merged
fdesbiens merged 1 commit intoOct 2, 2026
Merged
Conversation
The four libraries under libs/ were pinned at commits from the 6.5.0.202601 development series, so the samples on main built against libraries two releases behind the one they ship alongside. Each now points at its product's master as released in 6.5.2.202603, and the tracked branch in .gitmodules moves from dev to master to match. Both halves are needed: scripts/update-libs.sh advances each submodule to the head of its tracked branch, so leaving the branch at dev would pull development commits back over these pins the next time it runs. The MXChip entries are untouched. They carry no tracked branch and are pinned to the versions that board was validated against. Assisted-by: Claude Code (Opus 5) <[email protected]>
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.
The four libraries under
libs/were pinned at commits from the 6.5.0.202601 development series, so the samples onmainbuilt against libraries two releases behind the one they ship alongside.Each now points at its product's
masteras released in 6.5.2.202603 — ThreadX93387b0a, FileXcdc7a593, NetX Duo20046b12, USBXd947676a— and the tracked branch in.gitmodulesmoves fromdevtomasterto match.Both halves are needed.
scripts/update-libs.shadvances each submodule to the head of its tracked branch, so pinning the released commits while leaving the branch atdevwould let the next run pull development commits straight back over them. The script's own header describes this as the release-time procedure.The MXChip entries are untouched: they carry no tracked branch and are pinned to the versions that board was validated against.
After the release is published, the
devbranch pins move back to trackingdev.