All notable changes to Botloader are documented in this file.
The format is based on Keep a Changelog,
using a YEAR.MAJOR.MINOR version scheme (e.g. 2026.5.1):
- YEAR: the calendar year of the release
- MAJOR: incremented for significant releases within the year (resets each year)
- MINOR: incremented for smaller fixes/patches on top of a major release
-
Run the release script from a clean master checkout:
scripts/release.sh minor # or: major, or an explicit version like 2026.5.1It bumps the
VERSIONfile, moves the[Unreleased]changelog entries under the new version, and creates the release commit and tag. -
Push the release commit and tag with the command the script prints:
git push origin master v2026.5.1
-
CircleCI builds the images with the version embedded in the binary (
common::VERSION, also shown bybackend --version) and pushes them to Docker Hub tagged with the version (e.g.botloader/backend:2026.5.1).
- Release versioning:
YEAR.MAJOR.MINORversion embedded in the backend binary, reported viabackend --version, thebotloader_build_infometric, and the Sentry release field. CI publishes version-tagged Docker images on release tags. scripts/release.shfor cutting releases: bumps theVERSIONfile, rolls the changelog, and creates the release commit and tag.