From 5325fff667cfad8e6762f64720c0f4486534b5d0 Mon Sep 17 00:00:00 2001 From: Mark IJbema Date: Tue, 28 Apr 2026 17:33:17 +0200 Subject: [PATCH] docs: move GHCR follow-up out of RELEASING.md into the PR --- RELEASING.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 294a7a8075..c6b3d4fb1d 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -116,12 +116,3 @@ The following secrets must be configured in the repository: ### Concurrency The workflow uses concurrency control (`workflow-ref-bump/version`) to prevent parallel releases from conflicting. - -## One-Time Follow-Up After Renaming the Docker Image - -The CLI Docker image was renamed from `ghcr.io/kilo-org/kilo` to `ghcr.io/kilo-org/kilocode`. The first release after the rename will create a brand-new GHCR package; after that publish succeeds, do the following once: - -1. Open `https://github.com/orgs/Kilo-Org/packages/container/kilocode/package-settings`. -2. **Make the package public** — "Danger Zone" → "Change visibility" → Public. Without this, `docker pull` will return 401 for everyone. -3. **Connect it to the `kilocode` repo** — "Manage Actions access" / "Repository" → select `Kilo-Org/kilocode`. This makes the package appear under the repo's Packages sidebar and fixes the source repo shown in the GHCR UI. -4. (Optional) Deprecate the old `ghcr.io/kilo-org/kilo` package at `https://github.com/orgs/Kilo-Org/packages/container/kilo/package-settings` so users stop pulling from the archived-repo-linked package.