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: .github/ISSUE_TEMPLATE/---release.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,13 +19,13 @@ If the troubleshooting section does not contain the answer to the problem you en
19
19
-[ ] Ensure that the `go.mod` file references an officially released version of `kong/kubernetes-configuration` instead of directly depending on the main branch version.
20
20
-[ ] Ensure that all generators have run properly (e.g. `make generate manifests`) so that updates to things like CRDs are handled for the release, double check that all manifests from `config/samples/` still work as intended.
21
21
-[ ] Ensure GitHub PAT is still valid (see [GitHub PAT](#github-pat) below).
22
-
-[ ] Ask on the `team-k8s` Slack channel for granting the CI DockerHub account temporary permission to push images to the `kong/gateway-operator-oss` repository.
22
+
-[ ] Ask on the `team-k8s` Slack channel for granting the CI DockerHub account temporary permission to push images to the `kong/kong-operator` repository.
23
23
-[ ] From [GitHub release action][release-action], start a new workflow run:
24
24
- Set the `Use workflow from` to the release branch: e.g. `release/1.2.x`
25
25
- If you want to release a major version, set the `Use workflow from` to the `main` branch otherwise set it to the release branch.
26
26
- Set the `release` input set to the target version (e.g. `v1.2.0`).
27
27
-[ ] Wait for the workflow to complete.
28
-
-[ ] Once the workflow completes, ask for revoking the temporary permission to push images to the `kong/gateway-operator-oss` repository.
28
+
-[ ] Once the workflow completes, ask for revoking the temporary permission to push images to the `kong/kong-operator` repository.
29
29
-[ ] The CI should create a PR in the [Gateway Operator][kgo-prs] repo that bumps KGO version in `VERSION` file and manifests. Merge it.
30
30
-[ ] After the PR is merged, [release-bot][release-bot-workflow] workflow will be triggered. It will create a new GH release, as well as a release branch (if not patch or prerelease):
31
31
-[ ] Check the [releases][releases] page. The release has to be marked manually as `latest` if this is the case.
0 commit comments