Making Releases¶
- Typically
dev
would have been merged intostaging
, and code instaging
thoroughly tested. - Once everything is verified to be working, a release can be made.
-
Normally I would do a simple hard reset of
main
to the latest testedstaging
(ensure all cherry-picked hotfixes are also present on staging in this case):git checkout main git reset --hard origin/staging
Checklist¶
To make a new release of Field-TM, ensure the following is done:
- Code is pulled through to the
main
branch. - Enter the backend directory:
cd src/backend
. - Bump the version:
cz bump --check-consistency
- To make manual control of which version to bump, the
--increment PATCH
or--increment MINOR
flag can be used.
- To make manual control of which version to bump, the
- If the uv.lock file is relocked and breaks the commit,
then commit manually by copying the commit message printed
to the terminal:
git commit -m "bump: 2025.1.1 --> 2025.1.2"
then ensure the tag is presentgit tag 2025.1.2
- Push the latest commits and tag:
git push && git push --tag
- Create a new release on Github via the UI, based on the new tag.
- Ensure the Github workflow succeeds in creating the latest tagged image.