From d3edfce2f257a65a05682065e48d0b73576092b8 Mon Sep 17 00:00:00 2001 From: Lucas Kalil Date: Wed, 17 Jun 2026 11:45:44 -0300 Subject: [PATCH] docs: document APP_VERSION management pattern - Single source of truth: assets/js/i18n.js line 9 - Document when to bump (after notable changes/deploys) - Document how to bump (one-liner, semantic commit) - Explain rationale (explicit versioning, audit trail) --- .agents/project-memory.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.agents/project-memory.md b/.agents/project-memory.md index 410ac36..5814881 100644 --- a/.agents/project-memory.md +++ b/.agents/project-memory.md @@ -505,3 +505,10 @@ Follow `how-refresh-data.md` (project root). In short: - User communicates in English/Portuguese mix; docs in English per conventions. - **Ask before each build step** — never chain into the next step without explicit go-ahead. + +### App version management (2026-06-17) +- **Single source of truth:** `assets/js/i18n.js` line 9 — `const APP_VERSION = 'v1.0.1'` +- **Footer display:** both EN and PT footers now show the version (template literals); removed "all data lives in JSON files" message +- **When to bump:** after notable feature ships (stats stages, major bugfix, schema change, deploy to production) +- **How to bump:** edit line 9, commit with `refactor(footer): bump version to vX.Y.Z`, push +- **Why:** makes versioning explicit and easy to track; enables future release notes / changelog automation