76540dbdd1
When branching the "stable-x.y" branch, we need to do some quite specific changes to kata-deploy / kata-cleanup files, such as: * changing the tags from "latest" to "stable-x.y". * removing the kata-deploy / kata-cleanup stable files. However, after the branching is done, we need to get the `main` repo to its original state, with the kata-deploy / kata-cleanup using the "latest" tag, and with the stable files present there, and this commit ensures that, during the release process, a new PR is automatically created with these changes. Fixes: #3069 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