Skip to content

Commit 30def7d

Browse files
authored
Merge pull request #312 from bacongobbler/release-process
add release process
2 parents 63efe9c + 9677e2d commit 30def7d

File tree

1 file changed

+38
-0
lines changed

1 file changed

+38
-0
lines changed

RELEASE.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# spin-operator release process
2+
3+
The vast majority of the release process is handled after you push a new git tag.
4+
5+
First, let's start by setting some environment variables we can reference later.
6+
7+
```console
8+
export TAG=v0.x.0 #CHANGEME
9+
```
10+
11+
To push a tag, do the following:
12+
13+
```console
14+
git checkout main
15+
git remote add upstream [email protected]:spinkube/spin-operator
16+
git pull upstream main
17+
git tag --sign $TAG --message "Release $TAG"
18+
git push upstream $TAG
19+
```
20+
21+
Observe that the [CI run for that tag](https://github.com/spinkube/spin-operator/actions) completed.
22+
23+
Bump the Helm chart versions. See #311 for an example.
24+
25+
Next, you'll need to update the documentation:
26+
27+
```console
28+
git clone [email protected]:spinkube/documentation
29+
cd documentation
30+
```
31+
32+
Change all references from the previous version to the new version.
33+
34+
Contribute those changes and open a PR.
35+
36+
As an optional step, you can run a set of smoke tests to ensure the latest release works as expected.
37+
38+
Finally, announce the new release on the #spinkube CNCF Slack channel.

0 commit comments

Comments
 (0)