Project: KEDA (Orchestration & Management / Scheduling & Orchestration)
File: RELEASE-PROCESS.md

The release process of a new version of KEDA involves the following: Look at the [last release] in the releases page: For example, at the time of writing, it was 2.3.0 The next version will thus be 2.4.0 Add a new section in for the new version that is being released along with the new features, patches and deprecations it introduces. It should not include every single change but solely what matters to our customers, for example issue template that has changed is not important. Add the new released version to the list in `KEDA Version` dropdown in . Creating a new release in the releases page (https://github.com/kedacore/keda/releases) will trigger a GitHub workflow which will create a new image with the latest code (read note 2 below) and tagged with the next version (in this example 2.4.0). KEDA Deployment YAML file (eg. keda-2.4.0.yaml) is also automatically created and attached to the Release as part of the workflow. Note: The container registry repo with all the different images can be seen Note 2: Depending on the release type (minor version or hotfix), the tag should be created from main (for minor version releases) or from version branch (for hotfix releases) Every release should use the template provided below to create the GitHub release and ensure that a new GitHub Discussion is created. ### IMPORTANT Remember to make the following changes to the template: Replace `INSERT-CORRECT-VERSION` (there are two occurrences in the template) with the new-release ID Update the list of new contributors Here's the template: ```markdown We are happy to release KEDA INSERT-CORRECT-VERSION Here are some highlights: <list highlights> Here are the new deprecation(s) as of this release: <list deprecations> Learn how to deploy KEDA by reading . The next KEDA release is currently being estimated for <date>, learn more in our

<list items> <list items> <list items> <list items> <generated new contributors info> ``` In order to generate a list of new contributors, use the `Auto-generate release notes` GitHub feature of the release. <details> <summary>Screenshot</summary> </details> Publish documentation for new version on https://keda.sh. For details, see . Note: During hotfix releases, this step isn't required as we don't introduce new features In order to continuously scan our new container image, they must be imported in our for all newly introduced tags. Prune old versions of images. Keep only one version for a 3 last minor releases (eg. keep only 2.10.1, 2.11.1 and 2.12.0). Learn more on how to do this through the . Note: Remember to enable the check `Without issues` in order to get the new version listed since probably it hasn't got any issue. Before we can release our new Helm chart version, we need to prepare it: Update the `version` and `appVersion` in our . Update the CRDs & Kubernetes resources based on the release artifact (YAML) Guidance on how to release it can be found in our . Create a new issue in stating that there should be a new release mirroring KEDA core release. As per our , we need to create a new shipping cycle in our with a target date in 3 months after the last cycle. We need to make sure that the current sprint's items are changed from status `Ready to ship` to `Done`. Lastly, the `Upcoming Release Cycles` overview in `ROADMAP.md` should be updated with the new cycle. In case of minor releases, we need to create the version branch (`release/v2.x`) from the release tag which will be used to include any required hotfix in the future. Prepare a tweet with some highlights and send it out on ! If you don't have access, ask a maintainer who has access to the account (see 1Password).