github/kata-containers
1
0
Fork 2
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-09-09 20:58:55 +00:00
Code Issues Projects Releases Wiki Activity

releases: Assume VERSION has the correct version to be released

Browse Source 
This is done in order to avoid having to push a commit to the main
branch, which is against the defined rules on GitHub.

By doing this, we need to educate ourselves to always bump the VERSION
file as soon as a release is cut out.

As a side effect of this change, we can drop the release-major and
release-minor workflows, as those are not needed anymore.

Fixes: #9064 - part IV

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
This commit is contained in:
Fabiano Fidêncio
2024-03-16 13:27:37 +01:00
parent 8ce50269fe
commit 12578f11bc
5 changed files with 14 additions and 95 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/Release-Process.md
View File

@@ -10,14 +10,11 @@ This document lists the tasks required to create a Kata Release.
### Check GitHub Actions
We make use of [GitHub actions](https://github.com/features/actions) in the
[minor](https://github.com/kata-containers/kata-containers/actions/workflows/release-minor.yaml)
and
[major](https://github.com/kata-containers/kata-containers/actions/workflows/release-major.yaml)
files from the
`kata-containers/kata-containers` repository to build and upload release
artifacts.
[release](https://github.com/kata-containers/kata-containers/actions/workflows/release.yaml)
file from the `kata-containers/kata-containers` repository to build and upload
release artifacts.
Those actions are manually triggered and are responsible for generating a new
The action is manually triggered and is responsible for generating a new
release (including a new tag), pushing those to the
`kata-containers/kata-containers` repository.