Skip to content

fix(release): publish firmware and Go clients automatically from main - #2

Merged
l-you merged 1 commit into
mainfrom
fix/automatic-releases
Oct 5, 2026
Merged

l-you merged 1 commit into
mainfrom
fix/automatic-releases

Conversation

@l-you

@l-you l-you commented Oct 5, 2026

Copy link
Copy Markdown
Member

A push to main now creates a version, firmware release assets and a matching Go client module tag after full Quality, without RELEASE_PUBLICATION_APPROVED, a personal token or a manual release PR.

  • Use pinned go-semantic-release v2.31.0 with its published SHA-256 and the standard GITHUB_TOKEN.
  • Call reusable firmware/image publishing from the same run; token-created tags do not need to trigger another workflow.
  • Preserve checksum, source/tag identity and the single full/partial-capable firmware artifact.
  • Document versioned screenclient/securetransport packages and direct encrypted ESP32 communication.

Validation: make workflows passed actionlint and existing firmware packaging regressions. GitHub Quality runs on this branch/PR.

Merging this PR activates automatic public GitHub firmware releases, Go module tags and GHCR images on main. Existing hardware firmware and provisioning are untouched.

Replace release-please approval and PAT requirements with pinned go-semantic-release using the standard workflow token. After full Quality, create one version tag and explicitly call firmware/image publication so token-created tag events are not required.

Keep artifact checksums, source/tag identity and full/partial application packaging; document versioned public Go client packages and encrypted ESP32 communication.

AI-Impact: co-developed
AI: cx
@l-you
l-you merged commit fc50a1b into main Oct 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant