chore: version 0.1 — changelog, VERSION file, agent workflow rules

This commit is contained in:
Jonas Miederer 2026-09-13 19:32:41 +02:00
parent df5c1e296c
commit c948657b25
3 changed files with 39 additions and 0 deletions

View file

@ -62,3 +62,24 @@ report = await sync_from_directory(session, lfx, settings.flows_dir)
## Git
When committing: `git add -A && git commit -m "<message>"` (conventional commits: `feat:`, `fix:`, `chore:`, `docs:`). When pushing: `git push` (branch is tracking `origin/main`).
## Versioning
- `VERSION` (repo root) is canonical — currently `0.1.0`.
- Backend: `backend/pyproject.toml` version; Frontend: `frontend/package.json` version — bump both together with VERSION on every release.
- SemVer: feat → minor (X.Y+1.0), fix → patch (X.Y.Z+1), breaking → major (X+1.0.0). Tag `vX.Y.Z` at release merge.
- Changelog: every user-visible change gets an `[Unreleased]` entry (Keep a Changelog categories) before commit; at release move it into `[X.Y.Z] - YYYY-MM-DD`.
## Git workflow
- New work branches from `main`: `feat/<short>` for features, `fix/<short>` for fixes.
- Push branch, open MR, merge `--no-ff` on green CI, delete branch.
- Never push directly to `main` for features or fixes.
## Web-dev digest
- Small batches: PR diff ≤ ~200 lines ideal; trunk-based with short-lived branches (above).
- Tests green before merge (definition of done); `npm run build` green for frontend.
- Docs in same PR as feature (README, AGENTS, CHANGELOG).
- Deprecate in minor, remove in next major; document Removed/Deprecated in CHANGELOG.
- Lockfiles (uv.lock, package-lock.json, compose pins) — don't drift without reason.