Skip to content

ci: fork-friendly GHCR Docker release workflow - #4

Merged
kubo6472 merged 2 commits into
mainfrom
cursor/release-docker-ghcr-01c3
Jun 15, 2026
Merged

ci: fork-friendly GHCR Docker release workflow#4
kubo6472 merged 2 commits into
mainfrom
cursor/release-docker-ghcr-01c3

Conversation

@kubo6472

@kubo6472 kubo6472 commented Jun 15, 2026

Copy link
Copy Markdown
Member

Summary

Adds a dedicated Release with Docker image to GHCR workflow that publishes Sofie Core container images under the repository running the action (e.g. ghcr.io/tojemoc/sofie-core-server-core), without hardcoding Sofie-Automation or blocking forks.

Tagging strategy

Trigger Image tags
Push to main latest + build-<run_number> (incrementing per workflow run)
Version tag (v**) <tag> only (e.g. v1.2.3) + GitHub Release

Changes

  • New .github/workflows/release-docker.yml
    • Triggers on workflow_dispatch, pushes to main, and version tags (v**)
    • Verifies the ref is on main before publishing
    • Builds and pushes server-core, playout-gateway, mos-gateway, and live-status-gateway to GHCR using ${GITHUB_REPOSITORY,,} for image names
    • Creates a GitHub Release on tags with docker pull instructions
  • Updated .github/workflows/node.yaml
    • Removes GHCR publishing (now handled by the release workflow)
    • Node CI still builds Docker images locally for validation and continues Docker Hub publishing when secrets are configured

Example images (on tojemoc/sofie-core)

Main build:

ghcr.io/tojemoc/sofie-core-server-core:latest
ghcr.io/tojemoc/sofie-core-server-core:build-42

Tagged release:

ghcr.io/tojemoc/sofie-core-server-core:v1.0.0
Open in Web Open in Cursor 

Move GHCR publishing out of Node CI into a dedicated release workflow
that uses the running repository for image names (e.g.
ghcr.io/tojemoc/sofie-core-server-core). No org gate — works on forks.

On version tags, the workflow verifies the tag is on main, builds and
pushes server-core and gateway images, and creates a GitHub Release
with docker pull instructions.

Co-authored-by: Jakub Doboš <kubo6472@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@kubo6472, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 31 minutes and 59 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bb1c2e07-b9df-4971-ba7a-c79eb3f94288

📥 Commits

Reviewing files that changed from the base of the PR and between a0d0fc5 and 8fb33f1.

📒 Files selected for processing (2)
  • .github/workflows/node.yaml
  • .github/workflows/release-docker.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cursor/release-docker-ghcr-01c3

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

On push to main, publish latest and build-<run_number> tags.
On version tag pushes, publish only the release tag (e.g. v1.2.3).

Co-authored-by: Jakub Doboš <kubo6472@users.noreply.github.com>
@kubo6472
kubo6472 marked this pull request as ready for review June 15, 2026 18:03
@kubo6472
kubo6472 merged commit 05d3915 into main Jun 15, 2026
43 checks passed
@kubo6472
kubo6472 deleted the cursor/release-docker-ghcr-01c3 branch June 15, 2026 18:04
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