@@ -44,11 +44,6 @@ For a **PATCH** release:
44
44
in the upcoming steps.
45
45
- Use ` git ` to cherry-pick all relevant PRs into your branch.
46
46
- Update ` pkg/generator/main.go ` with the new semver tag and any updates to the API review URL.
47
- - Run the following command ` BASE_REF=vmajor.minor.patch make generate ` which
48
- will update generated docs and webhook with the correct version info. (Note
49
- that you can't test with these YAMLs yet as they contain references to
50
- elements which wont exist until the tag is cut and image is promoted to
51
- production registry.)
52
47
- Create a pull request of the ` <githubuser>/release-x.x.x ` branch into the ` release-x.x ` branch upstream
53
48
(which should already exist since this is a patch release). Add a hold on this PR waiting for at least
54
49
one maintainer/codeowner to provide a ` lgtm ` .
@@ -64,11 +59,6 @@ For a **MAJOR** or **MINOR** release:
64
59
- Cut a ` release-major.minor ` branch that we can tag things in as needed.
65
60
- Check out the ` release-major.minor ` release branch locally.
66
61
- Update ` pkg/generator/main.go ` with the new semver tag and any updates to the API review URL.
67
- - Run the following command ` BASE_REF=vmajor.minor.patch make generate ` which
68
- will update generated docs and webhook with the correct version info. (Note
69
- that you can't test with these YAMLs yet as they contain references to
70
- elements which wont exist until the tag is cut and image is promoted to
71
- production registry.)
72
62
- Verify the CI tests pass before continuing.
73
63
- Create a tag using the ` HEAD ` of the ` release-x.x ` branch. This can be done using the ` git ` CLI or
74
64
Github's [ release] [ release ] page.
@@ -79,11 +69,6 @@ For a **MAJOR** or **MINOR** release:
79
69
For an ** RC** release:
80
70
81
71
- Update ` pkg/generator/main.go ` with the new semver tag and any updates to the API review URL.
82
- - Run the following command ` BASE_REF=vmajor.minor.patch make generate ` which
83
- will update generated docs and webhook with the correct version info. (Note
84
- that you can't test with these YAMLs yet as they contain references to
85
- elements which wont exist until the tag is cut and image is promoted to
86
- production registry.)
87
72
- Include the changelog update in this PR.
88
73
- Merge the update PR.
89
74
- Tag the release using the commit on ` main ` where the changelog update merged.
0 commit comments