Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

📖 Update notes on post-release activities #445

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

📖 Update notes on post-release activities #445

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,11 @@ git push upstream ${RELEASE_TAG}

This will trigger a [release GitHub action](https://github.com/rancher/cluster-api-provider-rke2/actions/workflows/release.yml) that creates a release with RKE2 provider components.

## Tasks
4. Mark release as ready.

Published releases are initially marked as `draft`. If the published version is supposed to be `latest`, mark it so on the release [page](https://github.com/rancher/cluster-api-provider-rke2/releases/), while editing the release. Please note that we are using [semantic versioning](#versioning) while choosing `latest` version.

5. Perform mandatory [post-release activities](#prepare-main-branch-for-development-of-the-new-release), which will ensure contract `metadata.yaml` file is [up-to-date](#2-add-future-version-to-metadatayaml-for-example-if-v05-was-just-released-we-add-v06-to-the-list-of-releaseseries) in case of a future `minor/major` version change.

### Prepare main branch for development of the new release

Expand Down