Compare commits

...

2 Commits

Author SHA1 Message Date
Kay Yan
1c9add4897 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>
2026-04-24 09:46:46 +05:30
Ali Afsharzadeh
00a29dffc8 Add myself (guoard) as reviewer (#13197)
Signed-off-by: Ali Afsharzadeh <afsharzadeh8@gmail.com>
2026-04-23 17:48:47 +05:30
2 changed files with 2 additions and 1 deletions

View File

@@ -8,6 +8,7 @@ aliases:
kubespray-reviewers: kubespray-reviewers:
- cyclinder - cyclinder
- erikjiang - erikjiang
- guoard
- mzaian - mzaian
- tico88612 - tico88612
- vannten - vannten

View File

@@ -58,7 +58,7 @@ You can create a release note with:
export GITHUB_TOKEN=<your-github-token> export GITHUB_TOKEN=<your-github-token>
export ORG=kubernetes-sigs export ORG=kubernetes-sigs
export REPO=kubespray 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.). 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.).