Skip to content

Preserve Lambda ECR refs in release manifests#72

Merged
gontzess merged 1 commit into
mainfrom
gontzess/preserve-lambda-ecr-image-ref
May 6, 2026
Merged

Preserve Lambda ECR refs in release manifests#72
gontzess merged 1 commit into
mainfrom
gontzess/preserve-lambda-ecr-image-ref

Conversation

@gontzess
Copy link
Copy Markdown
Contributor

@gontzess gontzess commented May 6, 2026

Why

The release workflow now records lambda-arm64 image metadata for registry API ingest, but it rewrites the Lambda image ref to a short repo tag. C1 expects release metadata to carry a full or templated ECR image URI so it can resolve the account and region before Lambda deployment.

What this changes

  • Preserves the full Lambda ECR image ref from GoReleaser's digest output.
  • Builds the digest-pinned Lambda image URI from that same full ref.
  • Updates the extractor test to assert the deployable ECR ref is retained.

Validation

  • go test ./cmd/extract-images ./cmd/record-release
  • go test ./...
  • git diff --check

@gontzess gontzess marked this pull request as draft May 6, 2026 19:45
@gontzess gontzess marked this pull request as ready for review May 6, 2026 21:14
@gontzess gontzess merged commit 03c04b7 into main May 6, 2026
1 check passed
@gontzess gontzess deleted the gontzess/preserve-lambda-ecr-image-ref branch May 6, 2026 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants