Since patch recipes are now included with the CLI, is it necessary to release/cut new CLI versions every time a CVE is patched or a new hotfix is released in the Spring enterprise repository?
No, new versions of the CLI are not required for every CVE patch or enterprise repository update. The CLI is designed with two distinct commands to handle different update cadences:
advisor patch apply (available in an upcoming release)
advisor upgrade-plan apply:
settings.xml for the environment running the CLI must be configured with the Broadcom Enterprise Repository (or a local proxy) to resolve the proper versions of commercial artifacts.patch apply (higher frequency for security compliance) and one for upgrade-plan apply (lower frequency for feature upgrades).Accessing Spring Enterprise Release Notes and Changelogs - https://knowledge.broadcom.com/external/article/436475