From 8f5474d0547e757d957c29446b6c44f59a0521b0 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 28 Apr 2026 12:23:13 +0000 Subject: [PATCH 1/2] document release notes conventions for kbd shortcuts, same-release fixes, and revert rationale --- CLAUDE.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 6c0c2eeb..601e61c2 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -165,3 +165,6 @@ This installs dependencies and runs postinstall scripts (including the lefthook - Reference settings paths as `Settings... → Section → Option`. - Group related bullets next to each other (e.g. all Google Apps changes together). - Use sub-bullets for details: options list, defaults, keyboard shortcuts, behavior nuances. Always state the default for new options. +- Drop fixes to code newly introduced in the same release — a bug that only existed between merge and tag is invisible to users upgrading from the previous public release. +- Wrap keyboard shortcuts in `` tags and write them per platform: `Cmd+F on macOS, Ctrl+F on Windows/Linux`. +- When reverting or removing a previously released feature, include the reason inline so users who relied on it understand the change. From 7364de5277060a66611a944d69c32c689d4508ca Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 28 Apr 2026 12:26:52 +0000 Subject: [PATCH 2/2] note that release notes should be wrapped in a fenced code block for copy-paste --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 601e61c2..516cf90a 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -152,7 +152,7 @@ This installs dependencies and runs postinstall scripts (including the lefthook ## Release Notes - Release notes live only on GitHub Releases — do not commit a `RELEASE_NOTES.md` or `CHANGELOG.md` file. Match the style of recent published releases at https://github.com/zoidsh/meru/releases. -- Output the release notes in chat for pasting into the GitHub release — do not write them to a file in the repo. +- Output the release notes in chat for pasting into the GitHub release — do not write them to a file in the repo. Wrap the notes in a fenced markdown code block so the raw markdown can be copied directly into the GitHub release. - Structure: use `## Added`, `## Changed`, `## Fixed`, `## Internal Changes` sections (in that order, omit unused ones). Skip `## Internal Changes` entirely when nothing affects end users (e.g. CI, CLAUDE.md, repo tooling). - Classify each change correctly: - `Added` — new feature or capability