One of the major changes made for ModusToolbox™ version 3.x is that most BSPs are no longer Git repos when you create a version 3.x application. Instead, the BSP becomes owned by the application. This means you can change various aspects of the BSP as you see fit without having to create a custom BSP, because creating a version 3.x application effectively creates a custom BSP. As such, you will typically check the BSP into source control with the application.
ModusToolbox™ version 2.x BSPs are still Git repos, by default, and may be used by more than one application in a given workspace. In general, this means any change you make to a BSP creates a "dirty" repo, and those changes affect all the related applications. In this case, you will typically not check the version 2.x BSP into source control, since you can regenerate the BSP. For this reason, it is best to create a "custom BSP" for your needs.
Refer to the ModusToolbox™ tools package user guide for more details about ModusToolbox™ BSPs and applications.
This version of the Library Manager supports both ModusToolbox™ version 3.x and 2.x BSPs. The main difference is that the Version and Type fields are not applicable and cannot be changed for a 3.x BSP. See the Properties tab section later in this document for descriptions of these fields.