docs: fix release-notes command in release guide (#13211 )

The documented example still uses the removed --required-author flag and misses --repo-path, which breaks with current release-notes binaries. Update it to use the generate subcommand and point at the local checkout. Signed-off-by: Kay Yan <kay.yan@daocloud.io>
Add myself (guoard) as reviewer (#13197 )
2026-04-25 03:35:24 -02:30 · 2026-04-24 09:46:46 +05:30 · 2026-04-23 17:48:47 +05:30
2 changed files with 2 additions and 1 deletions
--- a/1
+++ b/1
@@ -8,6 +8,7 @@ aliases:
  kubespray-reviewers:
    - cyclinder
    - erikjiang
+    - guoard
    - mzaian
    - tico88612
    - vannten
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -58,7 +58,7 @@ You can create a release note with:
 export GITHUB_TOKEN=<your-github-token>
 export ORG=kubernetes-sigs
 export REPO=kubespray
-release-notes --start-sha <The start commit-id> --end-sha <The end commit-id> --dependencies=false --output=/tmp/kubespray-release-note --required-author=""
+release-notes generate --org "${ORG}" --repo "${REPO}" --repo-path "${PWD}" --start-sha <The start commit-id> --end-sha <The end commit-id> --dependencies=false --output=/tmp/kubespray-release-note
 ```

 If the release note file(/tmp/kubespray-release-note) contains "### Uncategorized" pull requests, those pull requests don't have a valid kind label(`kind/feature`, etc.).