opensource/kilocode
3
0
Fork 0
mirror of https://github.com/Kilo-Org/kilocode.git synced 2026-08-28 11:05:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: move GHCR follow-up out of RELEASING.md into the PR

Browse Source
This commit is contained in:
Mark IJbema
2026-04-28 17:33:17 +02:00
parent cbe55103b1
commit 5325fff667
1 changed files with 0 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
RELEASING.md
-9
View File
@@ -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.