Skip to content

ci(docker-release): add optional GHCR dual-registry push#1

Merged
JSisques merged 1 commit into
mainfrom
ci/docker-release-ghcr
May 15, 2026
Merged

ci(docker-release): add optional GHCR dual-registry push#1
JSisques merged 1 commit into
mainfrom
ci/docker-release-ghcr

Conversation

@JSisques

Copy link
Copy Markdown
Contributor

Summary

  • Add opt-in push_ghcr and ghcr_image_name inputs to the shared docker-release workflow
  • Login to GHCR with GITHUB_TOKEN when enabled; unified tag list for Docker Hub + GHCR
  • Guard against duplicate git tags after version bump
  • Default push_ghcr: false — no behavior change for existing consumers (prompt-service)

Test plan

  • Review tag computation for stable vs alpha/beta/rc channels
  • Confirm prompt-service release workflow still validates (inputs unchanged)
  • Merge before sisques-labs/aws-local-ui release consumer PR

Depends on

Unblocks: sisques-labs/aws-local-ui PR for release.yml (needs these inputs on main)

Made with Cursor

Extend the reusable docker-release workflow with push_ghcr and
ghcr_image_name inputs so consumers can publish to GHCR alongside
Docker Hub. Unify tag computation, add duplicate-tag guard, and grant
packages: write when GHCR push is enabled.

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

1 participant