feat(ci): publish node Docker image to GHCR on release#378
Conversation
On every published release this triggers the reusable build-node workflow in k-nuth/docker-images, which builds and pushes ghcr.io/k-nuth/kth:<tag> and :latest. Runs with the built-in GITHUB_TOKEN (packages: write); no Personal Access Token or repository secret is needed. workflow_dispatch is also provided to (re)build a specific version on demand. Requires the companion PR adding build-node.yml to k-nuth/docker-images to be merged first.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
Publish the node Docker image on release
Adds
.github/workflows/docker-release.yml: on every published release it calls the reusablebuild-nodeworkflow ink-nuth/docker-images, which builds and pushesghcr.io/k-nuth/kth:<tag>and:latest. So tagging a release is all that's needed — theimage appears under this repo's Packages automatically.
GITHUB_TOKEN(packages: write).workflow_dispatchis included to (re)build a specific version on demand.Order: this depends on the companion PR that adds
build-node.ymltok-nuth/docker-images— please merge that one first. After it's in, this can be triedimmediately via the Actions tab (workflow_dispatch) without cutting a release.