fix(ci): merge release + Docker build into one job#28
Merged
KailasMahavarkar merged 1 commit intomainfrom Apr 10, 2026
Merged
Conversation
GITHUB_TOKEN-created releases do not re-trigger the release: workflow event (GitHub blocks this to prevent loops), so build-and-push-image never fired after auto-release. Merges release creation and Docker build into a single release-and-publish job. Both steps are gated on steps.check.outputs.new == 'true' so they only run when the version in package.json is new. Also removes the release: trigger from the workflow since it is no longer needed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
KailasMahavarkar
added a commit
that referenced
this pull request
Apr 14, 2026
GITHUB_TOKEN-created releases do not re-trigger the release: workflow event (GitHub blocks this to prevent loops), so build-and-push-image never fired after auto-release. Merges release creation and Docker build into a single release-and-publish job. Both steps are gated on steps.check.outputs.new == 'true' so they only run when the version in package.json is new. Also removes the release: trigger from the workflow since it is no longer needed. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Problem
`GITHUB_TOKEN`-created releases do not re-trigger the `release:` workflow event — GitHub blocks recursive workflow triggers. So `build-and-push-image` (which was gated on `github.event_name == 'release'`) never fired after the auto-release job ran.
Result: `v1.1.0` was released but no Docker image was pushed to ghcr.io.
Fix
Merge release creation and Docker build into a single `release-and-publish` job. Both the `gh release create` and `docker/build-push-action` steps are gated on `steps.check.outputs.new == 'true'`, so they only execute when the version in `package.json` is new.
Also removes the now-unused `release: types: [published]` trigger.
Flow after this PR
```
push to main (version bumped) → verify → release-and-publish:
├── gh release create v1.x.x
├── docker login ghcr.io
├── extract metadata (tags)
└── build + push :v1.x.x :latest
push to main (no version bump) → verify → release-and-publish:
└── (all steps skipped, tag already exists)
pull_request → verify only
```
🤖 Generated with Claude Code