ci: build and publish on release tags, skip the duplicate branch run - #69
Merged
Merged
Conversation
The push trigger only listed branches, so a pushed release tag never started a run: the tag-aware steps (versioned docker image, :latest) had never executed, and 1.0.0 had to be published by hand via workflow_dispatch. Add the tag trigger. tag-release.sh pushes the release commit to main before the tag, which would now build and deploy the same release twice. A gate job skips branch runs whose pom carries a non-SNAPSHOT version; the tag run publishes those. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013JvovM6T4az5f5qy3rpTVg
✅ Deploy Preview for orbital-nebula canceled.
|
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
1 participant
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.
Tag pushes never triggered
build.yml(on.pushonly listedbranches), so no release has ever been built by CI from its tag — 1.0.0 had to be published today viaworkflow_dispatch --ref 1.0.0. This adds the tag trigger.tag-release.shpushes the release commit tomainand then the tag, which would now run the build twice. A smallgatejob skips branch runs whose root pom carries a non-SNAPSHOT version and leaves publishing to the tag run. Snapshot builds onmain, PR builds and tag builds are unaffected.🤖 Generated with Claude Code
https://claude.ai/code/session_013JvovM6T4az5f5qy3rpTVg