ci: publish GitHub release with artifact metadata on every tag - #230
Merged
Conversation
Tags produced ECR images and registered artifacts, but no GitHub release — the published digests were invisible to consumers. Add a finalize job that upserts a release for the tag whose body carries an Artifacts table for all three images (containers, scheduled-task, containers-datadog): tag, digest, and the copyable pinned image@digest reference. Idempotent: an existing release only gains the table once, and re-runs with the same digests no-op. Same information the chained release pipeline writes in scopes-lambda (actions-nullplatform release-publish-oci); hand-rolled here because this repo fans out three images with an ordering dependency and its tags are human-pushed rather than cut by release-please. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
fedemaleh
approved these changes
Aug 26, 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
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
Companion to nullplatform/actions-nullplatform#93 and nullplatform/scopes-lambda#41, bringing this repo's releases up to the same standard: every tag now gets a GitHub release whose body lists each published image with its digest and a copyable pinned reference.
Today a tag push publishes 3 images to ECR and registers artifacts, but creates no GitHub release at all — consumers have nowhere to see or copy what was published.
Change
New
finalize-releasejob after the three publish + register jobs. It upserts the release for the tag:<tag>whose notes are the Artifacts table.--draft=false, repairing any draft orphaned by a tag delete/re-push).The table (one row per image — containers, scheduled-task, containers-datadog):
public.ecr.aws/nullplatform/scopes/containers:vX.Y.Zsha256:…public.ecr.aws/nullplatform/scopes/containers@sha256:…permissions.contentsgoesread→write(needed to create/edit releases).Unlike scopes-lambda this repo cannot adopt the chained
release-publish-ocireusable workflow as-is: it fans out three images with an ordering dependency (datadog overlay isFROMthe containers base) and its tags are human-pushed (no release-please), so the tag trigger works fine here — only the release upsert was missing.Test plan
🤖 Generated with Claude Code