You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: RELEASE-PROCESS.MD
+9-9
Original file line number
Diff line number
Diff line change
@@ -5,26 +5,29 @@ The release process of a new version of KEDA involves the following:
5
5
## 0. Prerequisites
6
6
7
7
Look at the last released version in the releases page: https://github.com/kedacore/keda/releases
8
-
For example: currently it is 2.0.0
9
-
The next version will thus be 2.1.0
8
+
For example: currently it is 2.3.0
9
+
The next version will thus be 2.4.0
10
10
11
11
## 1. Changelog
12
12
13
13
Provide a new section in `CHANGELOG.md` for the new version that is being released along with the new features, patches and deprecations it introduces.
14
14
15
15
It should not include every single change but solely what matters to our customers, for example issue template that has changed is not important.
16
16
17
-
## 2. Publish documentation for new version
17
+
## 2. Add the new version to GitHub Bug report template
18
+
Add the new released version to the list in `KEDA Version` dropdown in [3_bug_report.yml](https://github.com/kedacore/keda/blob/main/.github/ISSUE_TEMPLATE/3_bug_report.yml).
19
+
20
+
## 3. Publish documentation for new version
18
21
19
22
Publish documentation for new version on https://keda.sh.
20
23
21
24
See [docs](https://github.com/kedacore/keda-docs#publishing-a-new-version).
22
25
23
-
## 3. Create KEDA release on GitHub
26
+
## 4. Create KEDA release on GitHub
24
27
25
-
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.1.0).
28
+
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).
26
29
27
-
KEDA Deployment YAML file (eg. keda-2.1.0.yaml) is also automatically created and attached to the Release as part of the workflow.
30
+
KEDA Deployment YAML file (eg. keda-2.4.0.yaml) is also automatically created and attached to the Release as part of the workflow.
28
31
29
32
> Note: The Docker Hub repo with all the different images can be seen here: https://hub.docker.com/r/kedacore/keda/tags
30
33
@@ -62,9 +65,6 @@ Learn how to deploy KEDA by reading [our documentation](https://keda.sh/docs/INS
62
65
- <list items>
63
66
```
64
67
65
-
## 4. Add the new version to GitHub Bug report template
66
-
Add the new released version to the list in `KEDA Version` dropdown in [3_bug_report.yml](https://github.com/kedacore/keda/blob/main/.github/ISSUE_TEMPLATE/3_bug_report.yml).
67
-
68
68
## 5. Update Helm Charts
69
69
70
70
Update the `version` and `appVersion` in our [chart definition](https://github.com/kedacore/charts/blob/master/keda/Chart.yaml).
0 commit comments