fix(ci): move docker publish into release-please workflow#15
Merged
jordangarrison merged 2 commits intomainfrom Mar 7, 2026
Merged
fix(ci): move docker publish into release-please workflow#15jordangarrison merged 2 commits intomainfrom
jordangarrison merged 2 commits intomainfrom
Conversation
Runs `mix setup` automatically on first shell entry per worktree, gated by a `_build/.setup_done` marker file. Skips on subsequent entries.
The publish.yml workflow triggered on `release: [published]` never fired because releases created by the default GITHUB_TOKEN do not propagate events to other workflows (GitHub security feature). Move the Docker build & push into the release-please workflow as a dependent job that runs when `release_created` is true, using the `tag_name` output for the image version tag. Convert publish.yml to a workflow_dispatch fallback for manual re-publishing of a specific release tag.
Merged
jordangarrison
pushed a commit
that referenced
this pull request
Mar 7, 2026
🚀 Merging this PR will create a new release --- ## [0.3.0](v0.2.0...v0.3.0) (2026-03-07) ### Features * add paginated full views for user PRs and commits ([#13](#13)) ([2377eca](2377eca)) ### Bug Fixes * **ci:** move docker publish into release-please workflow ([#15](#15)) ([5634121](5634121)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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.
Summary
release-please.ymlworkflow as a dependentpublishjob that runs whenrelease_createdis truetag_nameoutput from release-please to version-tag the Docker image (e.g.v0.3.0)publish.ymlfromrelease: [published]trigger (which never fires due to GITHUB_TOKEN limitations) toworkflow_dispatchfor manual re-publishingRoot Cause
When release-please creates a GitHub release using the default
GITHUB_TOKEN, the resultingrelease: [published]event does not trigger other workflows. This is a GitHub security feature to prevent infinite workflow loops. Thepublish.ymlworkflow was never running.Test Plan
publishjob runs in the Release Please workflowlatestand version tagsPublish Releaseworkflow can be manually triggered viaworkflow_dispatch