From cf2b5acd3ee258af83bbcdb9b8dd7d76695db3a7 Mon Sep 17 00:00:00 2001 From: Barely Removable Date: Mon, 31 Aug 2026 07:45:42 -0700 Subject: [PATCH] Document that every commit should bump APP_VERSION Keeps the footer version string a trustworthy signal that a deploy actually landed, per deploy-arr-summary verification steps. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_017kn4ZaFd6RCnbMewMyMsfe --- CLAUDE.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 10ca8d5..5e06912 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -202,6 +202,13 @@ See the `deploy-arr-summary` skill for the Forgejo push-to-deploy pipeline, manual container restart steps, deploy verification, and the Nginx Proxy Manager / TLS setup and its Cox-port-80/DNS-01 constraint. +**Every commit should be matched with a version change.** Bump +`APP_VERSION` / `APP_VERSION_DATE` near the top of `app.py` as part of +the same commit. This is what makes the footer (`v · +`) a trustworthy signal that a given deploy actually +landed — a commit without a version bump can't be distinguished from +"not deployed yet" by looking at the live site. + ## Logins See the `manage-accounts` skill for the multi-user vs. legacy