Skip to content

ci: publish a sha tag for any ref, and keep latest for releases - #177

Merged
TITeee merged 1 commit into
mainfrom
ci/image-sha-tags
Nov 16, 2026
Merged

TITeee merged 1 commit into
mainfrom
ci/image-sha-tags

Conversation

@TITeee

@TITeee TITeee commented Nov 16, 2026

Copy link
Copy Markdown
Owner

Summary

  • A run started by hand now takes a ref: a release tag, or a branch or commit. A branch or commit publishes only sha-<7 digits>, so a build of main can be used without cutting a release.
  • A run by hand no longer moves latest; it stays with a pushed release tag (v*).
  • A new prepare job pins the ref to one commit, so both platforms build the same source.

Tags

Started by Tags
pushing a release tag <version>, <major>.<minor>, latest, sha-<7>
by hand, ref=v0.7.0 0.7.0, 0.7, sha-<7>
by hand, a branch or commit sha-<7>

A run started by hand takes a ref: a release tag, or a branch or commit.
A branch or commit publishes only sha-<7 digits> of the commit, so a
build of main can be used without cutting a release. A run by hand no
longer moves latest, which stays with a pushed release tag. A new
prepare job pins the ref to one commit, so both platforms build the
same source.
@TITeee
TITeee merged commit f8d0fe9 into main Nov 16, 2026
4 checks passed
@TITeee
TITeee deleted the ci/image-sha-tags branch November 16, 2026 08:30
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