cloudbuild: update tag/release script #13
Merged
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.
As COSI is working to release v0.2.0 from the new monorepo, ensure images are built and released to staging that are useful for devs and vendor drivers dependent on COSI.
Keep 'main' and 'latest' tags that follow COSI main head that is useful for COSI devs and driver devs, as well as canary-type CI envs.
Keep 'release-*' tags that follow COSI release branches that are useful for CI envs.
Allow tagging COSI commits with standard semver tags like 'v0.2.0' that don't include the 'sidecar/' or 'controller/' prefixes. These tags will release both sidecar and controller images to staging while COSI maintainers talk to sig-storage about releasing individual images from monorepos using the standardized sig-storage prow image tooling.