Documentation
Onboarding
Getting Started
Power & Battery
Hardware & Components
Build & Assembly
Radio & RF Design
Frequencies & Regulations
Firmware & Software
USB & Connectivity
GPS & Navigation
Morse & Communication
Modes & Operation
Field Operations & Rescue
Building Effectively
Build Variants
Project & Reference
Docs Project & Reference Release Process

Release Process

Edit on GitHub

How firmware releases happen: version numbering, the changelog, the release checklist, and what users should do before updating.

Release Process

A release is a promise: this version is tested, documented and flashable by anyone. The process exists to keep that promise honest.

Version numbering

The firmware follows semantic versioning (see Changelog):

BumpWhen
MajorBreaking config or payload format (v4 to v5)
MinorNew features, backward compatible
PatchBug fixes

The release checklist

  1. All CI checks green (see CI/CD).
  2. The changelog updated with the new entries.
  3. The wiki’s version-specific pages reviewed (config format, migration notes).
  4. A bench test pass on the release candidate (see Two Beacon Bench Test).
  5. Tag the release; attach the firmware binary.

What users should do

Before updating:

  1. Read the changelog for the target version, especially migration notes.
  2. Back up your configuration (serial config dump, see Serial Monitor Guide).
  3. Flash, then verify: boot log clean, config loaded, one test burst decoded.

Rollback

If a release misbehaves:

  1. Flash the previous version.
  2. Factory reset (see Factory Reset and Recovery) to clear any new-format config.
  3. Report the problem (see Reporting Issues).