Add commit-based container tagging prereq to harden-zot-registry chain #230

Merged
eblume merged 1 commit from add-container-versioning-prereq into main 2026-02-20 18:26:28 -08:00
Owner

Summary

  • New Mikado card: adopt-commit-based-container-tags — replaces git-tag-triggered container builds with path-based main-branch triggers and manual workflow dispatch
  • Image tags become vX.Y.Z-<sha> (with -main suffix for main branch builds, -nix for Nix builds), tying versions to the actual bundled app version and exact source commit
  • container-tag-and-release mise task to be renamed to container-build-and-release, triggering workflow dispatch with the current HEAD SHA
  • Added as soft prereq to harden-zot-registry Mikado chain

Test plan

  • Pre-commit hooks pass (docs-check-index, docs-check-links, etc.)
  • Review card content for completeness

🤖 Generated with Claude Code

## Summary - New Mikado card: `adopt-commit-based-container-tags` — replaces git-tag-triggered container builds with path-based main-branch triggers and manual workflow dispatch - Image tags become `vX.Y.Z-<sha>` (with `-main` suffix for main branch builds, `-nix` for Nix builds), tying versions to the actual bundled app version and exact source commit - `container-tag-and-release` mise task to be renamed to `container-build-and-release`, triggering workflow dispatch with the current HEAD SHA - Added as soft prereq to `harden-zot-registry` Mikado chain ## Test plan - [x] Pre-commit hooks pass (docs-check-index, docs-check-links, etc.) - [ ] Review card content for completeness 🤖 Generated with [Claude Code](https://claude.com/claude-code)
New Mikado card: adopt-commit-based-container-tags. Replaces git-tag-triggered
builds with path-based main-branch triggers and manual workflow dispatch,
using commit-SHA-qualified image tags tied to the bundled app version.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit 6d7071e5ec into main 2026-02-20 18:26:28 -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!230
No description provided.