From 1db8b95ba40c6bb13383d04453fc409985e28ec3 Mon Sep 17 00:00:00 2001 From: Tommy Chow Date: Sun, 16 Aug 2026 12:26:57 -0700 Subject: [PATCH] docs(agents): keep in-app notes to three consecutive versions Drop from the oldest end so the file stays short without holes in the version list. Co-authored-by: Cursor --- AGENTS.md | 2 +- docs/release.md | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 9ff8a3c6..4495eb73 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -43,4 +43,4 @@ New or changed logic (stores, API clients, parsing, utils) ships with tests; ext ## Releases -When cutting a store or GitHub release, read `docs/release.md` and follow it. That playbook is repo-local, not a global skill. +When cutting a store or GitHub release, read `docs/release.md` and follow it. That playbook is repo-local, not a global skill. `assets/release-notes.md` keeps about three consecutive versions; drop from the oldest end, never skip. diff --git a/docs/release.md b/docs/release.md index 479f9a14..f9927590 100644 --- a/docs/release.md +++ b/docs/release.md @@ -26,6 +26,8 @@ Do not put `AGENTS.md` or other docs in that commit. Write for someone opening the app, not the commit log. Match the latest shipped version's voice (`Added` / `Improved` / `Fixed`). Skip CI, Flutter upgrades, codegen, and anything a user wouldn't notice; the GitHub compare link is the rest. +Keep about three most recent versions, consecutive. Drop from the oldest end. Never skip a version in the middle. GitHub releases keep the full history. + - Features that didn't exist last release. Improvements only for behavior that already shipped — gating a new feature (opt-in permissions, an Enable flow) is not an improvement. - If you can't remember the user-facing symptom, it doesn't belong. - `[Android]` / `[iOS]` on platform-only lines. Cluster them: one tagged line at the end of its section, two or more adjacent.