ci: chain publish + artifact registration into the release run - #41
Merged
Conversation
The tag-push publish workflow never fired on release: release-please creates tags with GITHUB_TOKEN and GitHub does not trigger workflows from bot-token events. The manual delete/re-push workaround flipped the affected releases (v0.3.0, v0.3.1) into Draft state. Adopt actions-nullplatform's release-publish-oci: release-please, docker build+push to ECR, np artifact registration, and release finalize (artifact metadata appended to the body, release force- published) all chained in one run. publish-image.yml becomes a workflow_dispatch-only fallback for backfilling existing tags. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 25, 2026
release-publish-oci now accepts existing_tag (skip release-please, publish + finalize an already-created tag), which covers everything publish-image.yml's manual fallback did — and also writes the artifact metadata into the release, which the fallback never did. One workflow, one path; workflow_dispatch exposes the recovery mode. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Sep 2, 2026
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
First consumer of nullplatform/actions-nullplatform#93 — fixes the release pipeline at the root:
GITHUB_TOKEN; GitHub never fires workflows from bot-token events, sopublish-image.yml(on: push: tags) stayed silent. The delete/re-push workaround triggered it once but flipped v0.3.0 and v0.3.1 into Draft (deleting a tag drafts its release; re-pushing does not undo it).release.ymlnow calls the chainedrelease-publish-ociworkflow — release-please → docker build+push ECR →np artifact create→ release finalized with an Artifact section (image, digest, pinnedimage@digest, artifact id) and force-published. One run, no cross-workflow trigger, no PAT.publish-image.ymlbecomes aworkflow_dispatch-only fallback (input: existing tag) for backfills/recovery.Behavior preserved from the old caller:
release-type: terraform-module, README version updates on.Merge order
Merge actions-nullplatform#93 first (this references
release-publish-oci.yml@main).Test plan
🤖 Generated with Claude Code