fix(ci): inline the rds-postgres-db build — release run failed at startup - #13
Merged
Conversation
The release run died at startup (no jobs scheduled) after merge. The delta vs the sibling repos that worked: this caller referenced docker-build-push-ecr.yml a second time at a different ref than the chain's nested copy, plus hyphenated job ids in needs expressions. Both gone: the db image now builds in an inline buildx job (checkout at the tag, OIDC login to ECR Public, multi-arch push, digest captured via imagetools) with underscore job ids; registration and the release-notes append are unchanged. Co-Authored-By: Claude Fable 5 <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.
The release workflow hit startup_failure on main after #12 merged (no jobs scheduled — a workflow-plan rejection, not a job failure). This repo's caller was the only one of the four doing something unusual: it referenced
docker-build-push-ecr.ymla second time at a different ref than the chain's own nested copy, and used hyphenated job ids insideneeds.*expressions.Both suspects removed:
imagetools inspectpublish_db/finalize_db(underscores)Server image is untouched (still the chain). After merge, dispatch the workflow with
existing_tagset to the tag the failed run should have published, and the release backfills with both images.🤖 Generated with Claude Code