Skip to content

Commit 36e59f7

Browse files
committed
docs: document release process
1 parent 0fa6984 commit 36e59f7

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

docs/internal/release.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Release
2+
3+
To release a new version the following steps should be followed:
4+
5+
1. Create a new branch from `master` i.e. `release-<next semver>`. This
6+
will function as your release preparation branch.
7+
1. Add an entry to the `CHANGELOG.md` for the new release and change the
8+
`newTag` value in ` config/manager/kustomization.yaml` to that of the
9+
semver release you are going to make. Commit and push your changes.
10+
1. Create a PR for your release branch and get it merged into `master`.
11+
1. Create a `<next semver>` tag for the merge commit in `master` and
12+
push it to remote.
13+
1. Confirm CI builds and releases the newly tagged version.

0 commit comments

Comments
 (0)