Your enterprise wants to standardize a build-and-lint step used by dozens of repositories across several organizations. A platform team maintains the logic in a single private repository as a composite action. Consuming workflows reference it as 'my-org/ci-actions/build-lint@v2'. The platform team plans frequent bug fixes and occasional breaking changes, and wants consumers to automatically receive non-breaking fixes without editing their workflows, while being protected from breaking changes. Which release strategy for the central action best meets these requirements?