File tree Expand file tree Collapse file tree 1 file changed +9
-5
lines changed Expand file tree Collapse file tree 1 file changed +9
-5
lines changed Original file line number Diff line number Diff line change @@ -94,17 +94,21 @@ The release process is semi-automated.
94
94
95
95
### Step 1: Git Tag and GitHub Release
96
96
97
+ > [ !NOTE]
98
+ >
99
+ > Upon pushing the tag, a GitHub Action will do the following:
100
+ > - Build and publish the container image at ` quay.io/jetstack/venafi-agent ` ,
101
+ > - Build and publish the Helm chart at ` oci://quay.io/jetstack/charts/venafi-kubernetes-agent ` ,
102
+ > - Create a draft GitHub release,
103
+ > - Upload the Helm chart tarball to the GitHub release.
104
+
97
105
1 . Create a tag for the new release:
98
106
``` sh
99
107
export VERSION=v1.1.0
100
108
git tag --annotate --message=" Release ${VERSION} " " ${VERSION} "
101
109
git push origin " ${VERSION} "
102
110
```
103
- 2 . A GitHub action will see the new tag and do the following:
104
- - Build and publish the container image at ` quay.io/jetstack/venafi-agent ` ,
105
- - Build and publish the Helm chart at ` oci://quay.io/jetstack/charts/venafi-kubernetes-agent ` ,
106
- - Create a draft GitHub release,
107
- - Upload the Helm chart tarball to the GitHub release.
111
+ 2 . Wait until the GitHub Actions finishes.
108
112
3 . Navigate to the GitHub Releases page and select the draft release to edit.
109
113
1 . Click on “Generate release notes” to automatically compile the changelog.
110
114
2 . Review and refine the generated notes to ensure they’re clear and useful
You can’t perform that action at this time.
0 commit comments