Instruction file imported from AlphaStack-in/Traders-Guide-Academy (.cursor/rules/changelog.mdc). Copyright stays with the author.

Changelog on Every Commit

When making any commit that changes user-facing behavior, admin UI, client config, styling, assets, or API behavior, always update the changelog in the same commit before pushing.

Files to update

1. CHANGELOG.md — add bullets under ## [Unreleased] in the correct section (Added, Changed, Fixed, Removed). Match the existing Keep a Changelog style. When a version is cut, its header must be a full build timestamp, not just a date — ## [x.y.z] - YYYY-MM-DD HH:MM IST (24-hour, IST, matching the commit that actually ships it).
2. src/lib/changelog.ts — add a new entry at the top of the CHANGELOG array when the change is worth showing on the Admin → Changelog page. Its date field must also be a full build timestamp in the same format as build-info.ts's formattedBuildTime, e.g. "26 Aug 2026, 21:55 IST" — not a bare date. Bump package.json version (patch) so the deployed build matches the newest entry.

Commit workflow

1. Make the code/config change.
2. Update CHANGELOG.md (required for every product commit).
3. Update src/lib/changelog.ts + bump package.json patch version (continue the 1.0.x series from the latest entry — e.g. after 1.0.12 comes 1.0.13). The footer reads version from package.json via NEXT_APP_VERSION.
4. Commit everything together — do not leave changelog updates for a follow-up commit.

What to write

• One bullet per meaningful change; plain English; India/TGA context where relevant.
• No SignalFlow branding in TGA user-facing changelog text unless the change is internal/template-only.

Skip only when

• Pure tooling/docs with zero product impact (e.g. .gitignore, CI-only), or the user explicitly says not to changelog.