# Release Process ## Before Tagging - Confirm the default branch builds, runs, or flashes as documented. - Confirm no secrets, private data, generated dependency trees, or raw binaries are accidentally committed. - Confirm license and upstream provenance are documented. - Update CHANGELOG.md. - Attach binaries only as release assets with SHA256 checksums and source commit references. ## Release Notes Include: - Purpose of the release. - Commit hash or tag. - Build environment. - Known limitations. - Verification performed.