4adf93ef2c
During the release of 2.4.0-rc0 @egernst noticed an incositency in the way we handle release tags, as release candidates are being taken as "stable" releases, while both the kata-deploy tests and the release action consider this as "latest". Ideally we should have our own tag for "release candidate", but that's something that could and should be discussed more extensively outside of the scope of this quick fix. For now, let's align the code generating the PR for bumping the release with what we already do as part of the release action and kata-deploy test, and tag "-rc" as latest, regardless of which branch it's coming from. Fixes: #3847 Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
Release information
Introduction
This directory contains information of the process and tools used for creating Kata Containers releases.
Create a Kata Containers release
See the release documentation.
Release tools
update-repository-version.sh
This script creates a GitHub pull request (a.k.a PR) to change the version in all the Kata repositories.
For more information on using the script, run the following:
$ ./update-repository-version.sh -h
Update Kata projects to a new version
To update project version for Kata Containers, use the following:
# Set to the required version
$ new_version="a.b.c"
$ make bump-kata-version NEW_VERSION="${new_version}"
The makefile target bump-kata-version creates a GitHub pull request in the
kata-containers repository. The pull request is tested by the Kata CI to ensure the
entire project is working prior to the release. Next, the PR is approved and
merged by Kata Containers members.
tag_repos.sh
After Kata Containers repository is updated with a new version, it needs to be tagged.
The tag_repos.sh script is used to create tags for the Kata Containers repository.
The script creates an annotated tag for the new release version for the
following repositories:
- kata-containers