From c97f1a5c0046514fae4d92240dbceb765cbaef8a Mon Sep 17 00:00:00 2001 From: Ogulcan Celik Date: Tue, 19 May 2026 14:44:34 +0300 Subject: docs: finalize release readiness updates --- .pi/prompts/pre-release-audit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '.pi') diff --git a/.pi/prompts/pre-release-audit.md b/.pi/prompts/pre-release-audit.md index 11e42eb0..4858f598 100644 --- a/.pi/prompts/pre-release-audit.md +++ b/.pi/prompts/pre-release-audit.md @@ -53,7 +53,7 @@ Process: - Inspect commit bodies for issue reference lines in the form `refs #`. - Flag normal commits that use GitHub closing keywords like `fixes #`, `closes #`, or `resolves #`, because they close issues before release when they land on `master`. - For each shipped issue reference, check whether the changelog has a matching user-facing entry that mentions `#` when appropriate. - - For each merged external PR, check whether the changelog entry mentions the PR number and thanks the contributor in the existing style, e.g. `(#129, thanks @username)`. If the PR primarily ships an issue fix, include both the issue and PR numbers when useful, e.g. `(#128, #129, thanks @username)`. + - For each merged external human PR, check whether the changelog entry mentions the PR number and thanks the contributor in the existing style, e.g. `(#129, thanks @username)`. If the PR primarily ships an issue fix, include both the issue and PR numbers when useful, e.g. `(#128, #129, thanks @username)`. Do not add thanks text for maintainer-owned bots or automation accounts such as `kangal-bot` or `dependabot`. - Do not require or add GitHub closing keywords like `fixes #`, `closes #`, or `resolves #` to changelog entries or release notes. - List shipped issue references under `Issue references to close after release:` so the release operator can verify what release CI will close after the GitHub Release is published. - Flag stale entries that do not appear to correspond to shipped changes in the range. -- cgit v1.2.3