release-please

Automating firmware release workflows with Conventional Commits involves analyzing commit messages to determine version bumps, automatically updating changelogs, and creating release PRs. This process manages version files and publishes firmware binaries directly to GitHub Releases.

Semver version bumps for firmware projects are handled by parsing Conventional Commit prefixes to trigger Major, Minor, or Patch updates. The automation applies these bumps to configuration files like platformio.ini and Version.h during the release creation process.

Before automating GitHub Releases for your firmware binary, you need a release-please configuration file and a build step that compiles the firmware. The system uses these to update platformio.ini, Version.h, and publish the compiled binary.

Yes, Conventional Commits can manage OTA firmware deployment by automatically generating GitHub Releases that include the compiled firmware binary. Pushing commits to the main branch triggers the release pipeline, building and attaching the binary for OTA updates.

You should not use an automated release workflow for firmware versioning if your project lacks a strict Conventional Commits structure or if you need manual control over binary deployment. The system relies entirely on commit message prefixes to determine version bumps.