ci: switch to tag-triggered releases with production Docker tag #113
No reviewers
Labels
No Label
ai-changes-requested
ai-pr-opened
ai-reviewed
ai-reviewing
ai-working
in-next-release
status/in-progress
status/pr-open
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cal/major-domo-v2#113
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ci/tag-triggered-releases"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Switches from branch-push CI to tag-triggered releases. Merging to
mainno longer triggers a Docker build — pushing a CalVer tag does.Changes
.gitea/workflows/docker-build.ymlpush: tags: ['20*']instead ofpush: branches: [main]calveranddocker-tagscomposite action dependencies)productiontaggitea-tagstep (tags are pushed manually now)CLAUDE.mdnext-releasebranch references (branch retired)New release workflow
🤖 Generated with Claude Code