prepare-release

Firmware release preparation is automated by managing semantic version bumping, compiling all supported board targets, generating binary size reports, and creating standard format changelogs. The process assumes existing build scripts and test frameworks to execute end-to-end release steps efficiently.

Binary size reporting documents flash and RAM usage metrics for compiled firmware, including comparisons to previous versions. This tracking helps monitor memory footprint changes across supported board targets during the release cycle.

Comprehensive test execution for firmware releases involves running both host-side and on-device tests to verify functionality. The process assumes an existing test framework and validates all supported board targets before generating final release binaries with SHA256 checksums.

Release preparation workflows require existing version control, build scripts, and test frameworks to function properly. The process orchestrates these established components rather than creating them, ensuring all supported board targets compile and pass verification before deployment.

Flashing instructions for firmware releases are generated automatically after compiling board targets and creating release binaries with SHA256 checksums. The instructions detail how to flash the verified binary to target hardware, completing the release documentation alongside changelog and binary size report updates.

SHA256 checksums for release binaries provide cryptographic verification that compiled firmware matches the intended release version. Combined with binary size reports and changelog documentation, these checksums ensure release integrity before users flash binaries to target hardware.