Request a firmware review
Menu
Teams shipping firmware updates to devices in the field

Firmware release checklist from tag to rollout

The checks to run before a release leaves the building, in four groups: build, test, sign and record, and roll out.

Key characteristics

Items
17 in four groups
Groups
Build, test, sign and record, roll out
Output
Ticks on screen, CSV download, print
Runs
In your browser with nothing sent

Checklist: Firmware release checklist from tag to rollout

Tick items as you confirm them. Ticks stay on this page only; download the list when you are done.

Build
Test
Sign and record
Roll out

0 of 17 items confirmed

A firmware release is a promise to every device that receives it: this image was built from known source, tested against the ways updates fail, signed by you, and sent out in a way you can stop. This checklist holds the 17 checks behind that promise. It is written for release day, but most items depend on work done long before it, so read it once at the start of a project too.

How to use it

Open it for each release candidate you intend to ship. Tick an item only when it is confirmed for this build, not the last one. Download the CSV and keep it with the release notes; over a year those files become the record of how each release was made. Ticks are not saved if you leave the page.

The four groups

Build

The release is built by CI from a tagged commit, not on a laptop; the version string, build number and commit hash are embedded in the image; toolchain and dependency versions are recorded; and the build has been reproduced once to confirm the same output. The Reproducible Builds project defines a build as reproducible when anyone with the same source, build environment and instructions can recreate bit-by-bit identical output. That is what lets you rebuild an old release to investigate a field problem and know you are looking at the same binary.

Test

Unit tests and hardware-in-the-loop tests passed on this exact build; an update from the oldest supported version, not only the last one; an interrupted update, with power removed during the transfer and during the swap; a rollback forced by a failed self-test; and battery and current draw compared with the last release. The current check catches the release that works perfectly and halves battery life.

Sign and record

The image is signed with the production key in the signing service; the security counter is raised if the release fixes a vulnerability; a software bill of materials (SBOM) is generated for this build; and release notes are written for support and for customers. MCUboot can compare a security counter in each signed image with a value stored on the device and refuse images below it, so raising the counter is what stops a device being rolled back to the vulnerable version. For SBOM content, the reference to follow is the 2026 Minimum Elements for an SBOM, published by CISA, NSA, FBI and international partners in July 2026, which replaces the NTIA list from 2021.

Roll out

The wave plan, soak times and halt criteria are agreed; dashboards are ready for update success, reconnects and crashes; the support team knows what changed and how to spot problems; and the previous release stays available for rollback.

Reading the example

Example (fictional). Before the first wave of LW-1 firmware 1.1.0, Loamwick ran all 17 items. The interrupted-update test pulled power during the transfer from the gateway and during the swap. Because 1.1.0 makes probes refuse images signed with the retired development key, the team also confirmed that a probe running 1.1.0 refused one. The rollout went to 4 probes, then 12, then the remaining 24, with 48 hours between waves and a halt if any probe rolled back or went silent.

The order of the groups matters as much as the items. Signing comes after testing, so the production key only ever touches an image that passed. The rollout group comes last, but its dashboards have to exist before wave 1, or the soak time is just waiting.

Limits

  • It assumes the pipeline exists. Without a signing service, a tested rollback and a way to stage waves, most of this list cannot be ticked. Building those is a project, not a release step; see over-the-air updates.
  • It is per release, not per product. Product-level gates such as debug-port lockdown and factory programming are in the production readiness checklist.
  • A tick is only as good as its evidence. Keep the test records and logs behind each tick with the CSV.

What to do next

Write the notes with the release notes builder, check the version string with the version scheme builder and plan the waves with the staged rollout planner. Under sustaining releases, each release goes through this list and ends with a release report written for people who are not engineers. More in the updates and releases section of Field Update.

Send us your board and your plan.

A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.