Skip to content

ci(release): publish checksums for the tedge-onboard archives - #28

Merged
reubenmiller merged 1 commit into
mainfrom
feat/onboard-checksums
Nov 18, 2026
Merged

reubenmiller merged 1 commit into
mainfrom
feat/onboard-checksums

Conversation

@reubenmiller

Copy link
Copy Markdown
Contributor

Summary

c8y extensions install thin-edge/tiny-edge warns that the release does not publish checksums, so it can't verify the downloaded archive:

the release does not publish checksums, so tedge-onboard_0.8.0_darwin_arm64.tar.gz was not verified

A new onboard-checksums job in the release workflow runs after both onboard-tool builds have attached their archives. It downloads the tedge-onboard_* archives from the release, runs sha256sum on them, and attaches the result as tedge-onboard_<version>_checksums.txt. go-c8y-cli recognizes any file ending in _checksums.txt, and the name has no _<os>_<arch> suffix, so it isn't mistaken for a platform archive.

Testing

  • actionlint passes.
  • Ran the job's commands against the v0.8.0 archives, then installed through go-c8y-cli's binary-release install path with the resulting file. The archive was verified and its checksum recorded; a swapped archive was rejected with checksum mismatch.

This applies to releases from now on. v0.8.0 has no checksums file unless one is uploaded to it by hand.

🤖 Generated with Claude Code

Attach tedge-onboard_<version>_checksums.txt (sha256sum format) to each
release after all tedge-onboard archives are uploaded. go-c8y-cli finds
it and verifies the archive on "c8y extensions install", instead of
warning that the release does not publish checksums.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@reubenmiller
reubenmiller merged commit b456725 into main Nov 18, 2026
20 checks passed
@reubenmiller
reubenmiller deleted the feat/onboard-checksums branch November 18, 2026 05:15
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