morteza/TorbatYar
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
f89ca52e02
TorbatYar/docs/development/release-strategy.md
Mortezakoohjani 12c8615615 Ship enterprise Accounting FE/API with CRUD parity and production wiring. 
Adds accounting-service PATCH/archive, fiscal helpers, COA templates and setup status, plus SuperApp Accounting UI (DS, scoreboard, masters, vouchers, ledger, ops modules) with session refresh and HTTPS public API URLs.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-24 15:26:43 +03:30

1.2 KiB
Raw Blame History

Release Strategy

Semantic Versioning

  • MAJOR — breaking API/schema/contract changes
  • MINOR — backward-compatible features / modules
  • PATCH — fixes, docs, non-breaking hardening

Release Notes

Each release documents:

  • Features
  • Fixes
  • Migrations required
  • Config/env changes
  • Provider changes
  • Deprecations

Migration Order

  1. Backup (backup.md)
  2. Apply migrations per service in dependency order (typically Core → Identity → business services)
  3. Deploy services compatible with the new schema
  4. Smoke-test health and critical auth/onboarding paths
  5. Only then enable new feature flags

Rollback

  1. Prefer forward-fix migrations when possible
  2. Application rollback to previous image/tag
  3. Database downgrade only with tested Alembic downgrade path and restore point
  4. Document incident in progress / ops notes

Feature Flags

Use config/env or plan entitlements to gate incomplete modules. Do not ship half-enabled financial posting paths.

Related Documents