generated from falcosecurity/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Federico Di Pierro <[email protected]>
- Loading branch information
Showing
2 changed files
with
13 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# Release Process | ||
|
||
Our release process is fully automated using [Github actions](.github/workflows/release.yaml). | ||
|
||
When we release we do the following process: | ||
|
||
1. We decide together (usually in the #falco channel in [slack](https://kubernetes.slack.com/messages/falco)) what's the next version to tag | ||
2. Make sure that Makefile `FALCOSECURITY_LIBS_REVISION` points to an actual libs tag, since the release workflow will use the value as a badge | ||
3. A person with repository rights creates the Github Release with empty release notes | ||
4. The automated release workflow will start and generate the release notes | ||
|
||
> __NOTE:__ Since the release workflow uses [rn2md](https://github.com/leodido/rn2md) tool to generate release notes, make sure to always set correct `release-note` info in the PR body! |