Run publish-container only on release events #35
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
2 participants
Notifications
Due date
No due date set.
Reference
marvin8/xique!35
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-34-publish-container-release-only"
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?
The
publish-containerjob now carriesif: github.event_name == 'release'. On pushes tomainthe job is skipped (main runs go green again); on releases nothing changes — the job still builds and publishes the image from the tag ref, exactly as it did for0.1.0(run 1092).The
containerbuild-and-smoke-test job stays enabled on both events, keeping pre-release image validation on every push.Closes #34