Manually build and publish the Foreman proxy runtime image to GHCR from this repository and optionally trigger the Render image deploy for the exact pushed digest. Use only when the user explicitly asks to manually publish the Foreman proxy image, push the proxy image to GHCR, or redeploy Render from a freshly built proxy image. Do not use for normal CI-driven publishes, general Docker questions, or routine Render configuration work.
Use this skill for the repo's manual override path for the hosted proxy release. Follow the same image, tag, and deploy contracts that already exist in foreman-proxy/Dockerfile, render.yaml, and .github/workflows/foreman-proxy-image.yml.
foreman-proxy image from the current repository state and optionally roll Render forward to the exact pushed digest.foreman-server/exec-base.version, and a Render service id when deployment is requested.:main and :sha-<commit>, the pushed image digest, and optionally a Render deploy id and status.render.yaml, foreman-proxy/Dockerfile, and .github/workflows/foreman-proxy-image.yml.references/manual-publish.md if you need the exact repo contract or the safety rules.sha-<commit> tag from dirty state.main because the workflow also updates the :main tag. Only use --allow-non-main when the user explicitly asks to publish a non-main commit.--render-service-id, RENDER_SERVICE_ID, or RENDER_FOREMAN_SERVER_SERVICE_ID, stop and ask for it.foreman-server/scripts/publish-exec-base.sh instead of silently changing the base-image flow../scripts/publish-foreman-proxy.sh --render-service-id <render-service-id> --dry-run./scripts/publish-foreman-proxy.sh --skip-deploy./scripts/publish-foreman-proxy.sh --render-service-id <render-service-id>main branch only when the user explicitly asks:
./scripts/publish-foreman-proxy.sh --render-service-id <render-service-id> --allow-non-mainscripts/publish-foreman-proxy.sh: builds and pushes the image, captures the digest, and optionally triggers the Render deploy.references/manual-publish.md: concise source-of-truth notes for the repo-specific image and deploy contract.Do not widen this skill into a generic Render or Docker deploy helper. Keep it scoped to the Foreman proxy manual publish path.