From 817d1774fa827433ce58d4ff0a2a3a2f290508b1 Mon Sep 17 00:00:00 2001 From: Jorge Turrado Ferrero Date: Fri, 16 Dec 2022 16:44:56 +0100 Subject: [PATCH] chore: prepare release (#4019) --- .github/ISSUE_TEMPLATE/3_bug_report.yml | 1 + CHANGELOG.md | 20 ++++++++++---------- RELEASE-PROCESS.md | 8 +++++++- 3 files changed, 18 insertions(+), 11 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/3_bug_report.yml b/.github/ISSUE_TEMPLATE/3_bug_report.yml index 9b9d8bcfa82..df84abf5175 100644 --- a/.github/ISSUE_TEMPLATE/3_bug_report.yml +++ b/.github/ISSUE_TEMPLATE/3_bug_report.yml @@ -57,6 +57,7 @@ body: label: KEDA Version description: What version of KEDA that are you running? options: + - "2.9.1" - "2.9.0" - "2.8.1" - "2.8.0" diff --git a/CHANGELOG.md b/CHANGELOG.md index b71c28fc587..816df0cdc25 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -16,6 +16,7 @@ To learn more about active deprecations, we recommend checking [GitHub Discussio ## History - [Unreleased](#unreleased) +- [v2.9.1](#v291) - [v2.9.0](#v290) - [v2.8.1](#v281) - [v2.8.0](#v280) @@ -59,9 +60,7 @@ Here is an overview of all new **experimental** features: ### Fixes -- **General**: Properly retrieve and close scalers cache ([#4011](https://github.com/kedacore/keda/issues/4011)) -- **Azure Key Vault:** Raise an error if authentication mechanism not provided ([#4010](https://github.com/kedacore/keda/issues/4010)) -- **Redis Scalers**: Support `unsafeSsl` and enable ssl verification as default ([#4005](https://github.com/kedacore/keda/issues/4005)) +- **General**: TODO ([#TODO](https://github.com/kedacore/keda/issues/TODO)) ### Deprecations @@ -71,17 +70,18 @@ New deprecation(s): - TODO -Previously announced deprecation(s): - -- Default checkpointing strategy for Azure Event Hubs scaler `azureFunctions` is deprecated in favor of `blobMetadata` ([#XXX](https://github.com/kedacore/keda/issues/3596) | [Discussion](https://github.com/kedacore/keda/discussions/3552)) -- `metadata.type` is deprecated in favor of the global `metricType` for CPU, Memory, Datadog scalers ([#2844](https://github.com/kedacore/keda/issues/2844) | [Discussion](https://github.com/kedacore/keda/discussions/3002)) -- `rolloutStrategy` is deprecated in favor of `rollout.strategy` in ScaledJobs ([#3596](https://github.com/kedacore/keda/issues/3596) | [Discussion](https://github.com/kedacore/keda/discussions/3552)) -- Prometheus metrics on KEDA Metric Server are deprecated in favor of Prometheus metrics on KEDA Operator ([#3972](https://github.com/kedacore/keda/issues/3972) | [Discussion](https://github.com/kedacore/keda/discussions/3973)) - ### Other - TODO +## v2.9.1 + +### Fixes + +- **General**: Properly retrieve and close scalers cache ([#4011](https://github.com/kedacore/keda/issues/4011)) +- **Azure Key Vault:** Raise an error if authentication mechanism not provided ([#4010](https://github.com/kedacore/keda/issues/4010)) +- **Redis Scalers**: Support `unsafeSsl` and enable ssl verification as default ([#4005](https://github.com/kedacore/keda/issues/4005)) + ## v2.9.0 ### Breaking Changes diff --git a/RELEASE-PROCESS.md b/RELEASE-PROCESS.md index 2c4713c44f7..58ba2f7f7ed 100644 --- a/RELEASE-PROCESS.md +++ b/RELEASE-PROCESS.md @@ -23,12 +23,14 @@ Add the new released version to the list in `KEDA Version` dropdown in [3_bug_re ## 3. Create KEDA release on GitHub -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 and tagged with the next version (in this example 2.4.0). +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 [here](https://github.com/orgs/kedacore/packages?repo_name=keda) +> 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) + ### Release template Every release should use the template provided below to create the GitHub release and ensure that a new GitHub Discussion is created. @@ -92,6 +94,8 @@ In order to generate a list of new contributors, use the `Auto-generate release Publish documentation for new version on https://keda.sh. For details, see [Publishing a new version](https://github.com/kedacore/keda-docs#publishing-a-new-version). +> Note: During hotfix releases, this step isn't required as we don't introduce new features + ## 5. Setup continous container scanning with Snyk In order to continuously scan our new container image, they must be imported in our [Snyk project](https://app.snyk.io/org/keda/projects) for all newly introduced tags. @@ -119,6 +123,8 @@ We need to make sure that the current sprint's items are changed from status `Re 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. + ## 9. Tweet! 🐦 Prepare a tweet with some highlights and send it out on [@kedaorg](https://twitter.com/kedaorg)!