Ensure we check for CVEs before release
title: Creating a new release
---
-1. Go to the [releases](https://github.com/Azure/azure-service-operator/releases) page and draft a new release.
-2. In the tag dropdown, type the name of the new tag you'd like to create (it should match the pattern of previous releases tags, for example: `v2.0.0-beta.3`). The release target should be `main` (the default).
-3. Use the GitHub "auto-generate release notes" button to generate a set of release notes to work with. You will need to clean this up quite a bit before actually publishing it.
-4. If publishing an alpha, be sure to mark the release as a pre-release.
-5. Write a "Release Notes" section. You can edit the autogenerated section as a start. You can also look through the commits between the last release and now: `git log v2.0.0-beta.3..main`.
-6. Publish the release. This will automatically trigger a GitHub action to build and publish an updated Docker image with the latest manager changes.
-7. Ensure that the action associated with your release finishes successfully.
+1. Ensure that the [controller CVE scan action](https://github.com/Azure/azure-service-operator/actions/workflows/scan-controller-image.yaml) is green.
+2. Go to the [releases](https://github.com/Azure/azure-service-operator/releases) page and draft a new release.
+3. In the tag dropdown, type the name of the new tag you'd like to create (it should match the pattern of previous releases tags, for example: `v2.0.0-beta.3`). The release target should be `main` (the default).
+4. Use the GitHub "auto-generate release notes" button to generate a set of release notes to work with. You will need to clean this up quite a bit before actually publishing it.
+5. If publishing an alpha, be sure to mark the release as a pre-release.
+6. Write a "Release Notes" section. You can edit the autogenerated section as a start. You can also look through the commits between the last release and now: `git log v2.0.0-beta.3..main`.
+7. Publish the release. This will automatically trigger a GitHub action to build and publish an updated Docker image with the latest manager changes.
+8. Ensure that the action associated with your release finishes successfully.
# Cataloging breaking changes in a new release
