Skip to content

Flashberry release process

  1. Set the intended semantic version in VERSION.
  2. Add a dated section to CHANGELOG.md with the same version.
  3. Run make release-check CFG=flashberry.yml.

  4. Perform at least one full image build with a private configuration:

    make all CFG=flashberry.local.yml

  5. Verify the generated checksum:

    cd out sha256sum -c flashberry.img.zst.sha256

  6. Flash a disposable SD card and complete a boot smoke test.

  7. Commit the release changes, then create an annotated tag:

    git tag -a "v$(cat VERSION)" -m "Flashberry $(cat VERSION)"

  8. Push the commit and tag only after the hardware smoke test succeeds.

The automated checks cannot prove that a Raspberry Pi firmware/kernel combination boots on every board revision. The physical SD-card boot check is a required release gate.