Adopt commit-based container tags #232

Merged
eblume merged 1 commit from feature/adopt-commit-based-tags into main 2026-02-20 22:56:21 -08:00
Owner

Summary

  • Replace git-tag-triggered container builds with path-based triggers on main and workflow_dispatch
  • Image tags now encode upstream app version + commit SHA (vX.Y.Z-<sha>) for full traceability
  • Replace container-tag-and-release task with container-build-and-release (dispatches workflows via Forgejo API)
  • Update dagger publish() to accept commit_sha parameter
  • Update all docs and references to the new workflow

Deployment and Testing

  • Merge to main
  • mise run container-build-and-release <name> for each container to populate new-format tags
  • Verify tags in registry via mise run container-list
  • Existing images untouched — old tags remain available
## Summary - Replace git-tag-triggered container builds with path-based triggers on main and workflow_dispatch - Image tags now encode upstream app version + commit SHA (`vX.Y.Z-<sha>`) for full traceability - Replace `container-tag-and-release` task with `container-build-and-release` (dispatches workflows via Forgejo API) - Update dagger `publish()` to accept `commit_sha` parameter - Update all docs and references to the new workflow ## Deployment and Testing - [ ] Merge to main - [ ] `mise run container-build-and-release <name>` for each container to populate new-format tags - [ ] Verify tags in registry via `mise run container-list` - [ ] Existing images untouched — old tags remain available
Replace git-tag-triggered container builds with path-based triggers on
main and workflow_dispatch. Tags now encode the upstream app version and
commit SHA (vX.Y.Z-<sha>) for full traceability. The manual
container-tag-and-release task is replaced by container-build-and-release
which dispatches workflows via the Forgejo API.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit ffa8727660 into main 2026-02-20 22:56:21 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!232
No description provided.