ninja_hippo/arr-summary
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document that every commit should bump APP_VERSION

Browse source 
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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017kn4ZaFd6RCnbMewMyMsfe
This commit is contained in:
Barely Removable 2026-08-31 07:45:42 -07:00
parent 517559a460
commit cf2b5acd3e
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
CLAUDE.md
View file

@ -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 pipeline, manual container restart steps, deploy verification, and the
Nginx Proxy Manager / TLS setup and its Cox-port-80/DNS-01 constraint. 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<APP_VERSION> ·
<APP_VERSION_DATE>`) 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 ## Logins
See the `manage-accounts` skill for the multi-user vs. legacy See the `manage-accounts` skill for the multi-user vs. legacy