release.sh derives versions, no typing

patch/minor/major from latest tag (pubspec as-is for the first
release), bumps all pubspecs lockstep, commits, tags. Push with
--follow-tags and CI takes over. Docs updated to the flow.
This commit is contained in:
foxyz committed 2026-09-12 21:15:45 +03:00
1 parent 34e5dfb24c
commit b829f13437
3 files changed
+64 -6

No files matched your search

+3 -2
View File
@@ -24,8 +24,9 @@ pre-commit check. Tests run only when the code under test changed.
## Releases (user pushes tags, CI does the rest)
Release flow: release commit bumps `apps/desktop/pubspec.yaml` →
`git tag vX.Y.Z` → push tag → `.gitea/workflows/release.yml`
Release flow: `tool/release.sh [patch|minor|major]` derives the
version (no typing), bumps all pubspecs, commits, tags → review →
`git push --follow-tags` → `.gitea/workflows/release.yml`
builds, publishes the Forgejo release, commits
`updates/manifest.json` back. `tool/release_publish.sh` is the same
flow by hand. Workflows live in `.gitea/workflows` (this forge reads