ci: build (no push) on PR + main commits to catch Dockerfile breakage#3
Merged
Conversation
Catches Dockerfile breakage before cutting a release. Verify job builds without pushing on pull_request + push-to-main. Release job unchanged — still pushes on `release: [created]`. File renamed from a single-purpose "Release" workflow to a combined CI workflow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Currently the workflow only fires on
release: [created], so a broken Dockerfile is only discovered after cutting a release (as happened twice today with1.1.3). Add averifyjob that builds without pushing, triggered onpull_request+pushtomain. Release job unchanged.Renamed workflow from "Release" to "CI" to reflect dual purpose;
run-nameswitches betweenRelease <tag>andVerify <ref>based on event.Test plan
verifyjob, builds image, no push.buildjob fires, image lands on GHCR.