6e8350f71b
hub tool from github lets you show a particular tag that might exist in the repostiory. Switching our tag checking logic to use that instead of listing all tags and grepping for the one we want. For some reason the existing grep logic always fails to return the right code and always lands on the portion of the code to generate a new tag. Fixes: #519 Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
Release tools
This directory contains tools for Kata Containers releases.
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
Kata Containers is divided into multiple projects. With each release, all project versions are updated to keep the version consistent.
To update all versions for all projects, use the following:
$ make bump-kata-version NEW_VERSION=<new-version>
The makefile target bump-kata-version creates a GitHub pull request in the Kata repositories. These pull requests are 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 all the Kata repositories are updated with a new version, they need to be tagged.
The tag_repos.sh script is used to create tags for the Kata Containers
repositories. This script ensures that all the repositories are in the same
version (by checking the VERSION file).
The script creates an annotated tag for the new release version for the following repositories:
- agent
- proxy
- runtime
- shim
- throttler
The script also tags the tests and osbuilder repositories to make it clear which versions of these supporting repositories are used for the release.