The Version field doesn't apply to version 3.x BSPs, which are owned by the application. If this field is populated, it just displays information from the JSON file.
For all libraries and 2.x BSPs, you can select a dynamic "Latest X.Y release" or a fixed "X.Y.Z release" version. These represent tags for versions of libraries and version 2.x BSPs in GitHub repos:
- Dynamic – If you select a "Latest X.Y release " version, then it is dynamic. A ModusToolbox™ v2.x application will download and use the appropriate version specified in the manifest and attempt to resolve any potential conflicts with different versions. Using a "Latest" version means the item will update to the latest, backward-compatible version whenever you click the Library Manager Update button.
- Fixed – By selecting a specific "release-vX.Y.Z" version, you assign a fixed version of a specific, official release of the item that does not change, unless you manually change it.
When you create a new version 3.x application from an Infineon code example, the application converts libraries to use the "X.Y.Z release" version, by default. This ensures that they will not be updated automatically, unless you change the version to "Latest X.Y release."
When you open the Library Manager for an application and make any kind of change, the change summary displays in the console. If a "latest-vX.Y" tag has a newer version, the console displays a warning about the "latest-vX.Y" tag. It includes a hyperlink to open a dialog that explains how the "latest-vX.Y" tag auto-update works.
If you click Update, all items with the "latest-vX.Y" tag will be moved to the newer version, even if you didn’t make changes to them.