ci: fork-friendly GHCR Docker release workflow - #4
Conversation
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š <[email protected]>
|
Warning Review limit reached
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 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
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š <[email protected]>
2 participants
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 hardcodingSofie-Automationor blocking forks.Tagging strategy
mainlatest+build-<run_number>(incrementing per workflow run)v**)<tag>only (e.g.v1.2.3) + GitHub ReleaseChanges
.github/workflows/release-docker.ymlworkflow_dispatch, pushes tomain, and version tags (v**)mainbefore publishingserver-core,playout-gateway,mos-gateway, andlive-status-gatewayto GHCR using${GITHUB_REPOSITORY,,}for image namesdocker pullinstructions.github/workflows/node.yamlExample images (on
tojemoc/sofie-core)Main build:
Tagged release: