Repository navigation
Releases
ChristianHandy edited this page Nov 17, 2026
·
2 revisions
Releases are prepared by a workflow, published by another, and signed with the maintainer's own key.
| Kind | From | Example |
|---|---|---|
beta |
main |
1.8.1 → 1.9.0-beta.1 → 1.9.0-beta.2 |
release (main release) |
main |
1.9.0-beta.2 → 1.9.0 |
patch (subrelease) |
main |
1.8.0 → 1.8.1, only while main is not on a beta |
hotfix |
release/X.Y |
1.8.1 → 1.8.2 while main already has 1.9 work |
major |
main |
1.9.0 → 2.0.0 |
- Actions → Prepare release → Run workflow, choose the kind (optionally an exact version).
- In the finished run, click Open the pull request, then Create pull request. It sets the version and closes the changelog section.
- Merge it when the checks pass.
- Sign and push the tag (the commands are in the pull request):
git fetch origin && git checkout main && git pull
git tag -s vX.Y.Z -m "FleetPilot vX.Y.Z"git push origin vX.Y.Z
- The Release workflow builds the source archive, SBOM, signed APK, checksums and provenance and publishes the release.
Hotfix: the first run creates release/X.Y from the newest stable tag and stops. Merge the fix into that branch by pull request, run hotfix again, release, then merge release/X.Y back into main.
The workflow refuses to run when nothing is under Unreleased in the changelog. Details: CONTRIBUTING.md → Releases.
FleetPilot is GPL-3.0-or-later. Wiki pages summarise the documentation in the repository, which is authoritative. Found something wrong? Open an issue.
Use FleetPilot
Help build it
Links