From 56bf4933e7b5892c3d85f339aa6f076b7af36bd7 Mon Sep 17 00:00:00 2001 From: Leonardo Di Giovanna Date: Tue, 17 Jun 2025 11:57:34 +0200 Subject: [PATCH] docs(RELEASE.md): fix `rn2md` command documentation Signed-off-by: Leonardo Di Giovanna --- RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 6a831c90..801c1ebb 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -116,7 +116,7 @@ The release PR is meant to be made against the respective `release/M.m.x` branch - If any, manually correct it then open an issue to automate version number bumping later - Versions table in the `README.md` updates itself automatically - Generate the change log using [rn2md](https://github.com/leodido/rn2md): - - Execute `rn2md -o falcosecurity -m -r falco` + - Execute `rn2md -r falcosecurity/falco -m M.m.p -b release/M.m.x` - In case `rn2md` emits error try to generate an GitHub OAuth access token and provide it with the `-t` flag - Add the latest changes on top the previous `CHANGELOG.md` - Submit a PR with the above modifications @@ -129,7 +129,7 @@ The release PR is meant to be made against the respective `release/M.m.x` branch Core maintainers and/or the release manager can decide to publish pre-releases at any time before the final release is live for development and testing purposes. -The prerelease tag must be formatted as `M.m.p-r`where `r` is the prerelease version information (e.g. `0.35.0-rc1`.) +The prerelease tag must be formatted as `M.m.p-r` where `r` is the prerelease version information (e.g. `0.35.0-rc1`.) To do so: