From ecf4f9037ea4edffc7fc76d2325e716044d73d33 Mon Sep 17 00:00:00 2001 From: Mohamed Boudra Date: Thu, 25 Jun 2026 12:14:15 +0700 Subject: [PATCH] docs(release): document release previews --- docs/release.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/release.md b/docs/release.md index 3fb93be80..f3fe799c9 100644 --- a/docs/release.md +++ b/docs/release.md @@ -27,6 +27,7 @@ Rules that apply to both steps: - No code changes bundled into the changelog commit or the release commit. Code shims live in their own commit, reviewed on their own merits. - A sanity-check finding is information, not a directive. The agent surfaces it; the user decides. - Invoking a release skill is intent to start the flow, not blanket authorization to publish. +- If the user asks for a release preview, show the prospective changelog/release contents and answer questions, but do not commit, tag, publish, or run release commands until they explicitly authorize the release. ## Two paths