From 2d22e08a1eac865bac458ef1dc49cf6f1ff2fb4f Mon Sep 17 00:00:00 2001 From: shankar0123 Date: Mon, 4 May 2026 00:09:28 +0000 Subject: [PATCH] =?UTF-8?q?release:=20v2.0.68=20=E2=80=94=20image=20regist?= =?UTF-8?q?ry=20path=20moved=20to=20ghcr.io/certctl-io?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Image registry path changed. Starting this release, container images publish to `ghcr.io/certctl-io/certctl-server` and `ghcr.io/certctl-io/certctl-agent`. Existing pulls from `ghcr.io/shankar0123/certctl-{server,agent}:` continue to work for previously-published tags (the registry never deletes images), but the `:latest` tag at the old path stops moving forward at this release. Operators must update `docker pull` paths, `docker-compose.yml` `image:` keys, or Helm `image.repository` values to receive future updates. Old `git clone` / `git push` / install-script / API URLs continue to redirect forever — only the container-registry path changed. This is the only operator-action-required change in v2.0.68. Other changes since v2.0.67 are cosmetic URL refreshes after the GitHub org transfer (shankar0123 → certctl-io, 2026-05-03) and a contextcheck lint fix in the agent. The release.yml workflow's IMAGE_NAMESPACE env var was swept to certctl-io as part of the URL refresh, so the next release auto-pushes to the new ghcr.io path; verified via `grep -n IMAGE_NAMESPACE .github/workflows/release.yml` showing `IMAGE_NAMESPACE: certctl-io`. Adds a top-of-file v2.0.68 entry to CHANGELOG.md as a one-time migration callout. The existing "no hand-edited per-version changelog" policy text is preserved below — that policy applies to per-version entries; this is a one-time critical migration notice that needs to be visible to operators doing diligence by reading CHANGELOG.md. --- CHANGELOG.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 44e0751..6ef9d43 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,13 @@ # Changelog +## v2.0.68 — Image registry path changed ⚠️ + +> **Image registry path changed.** Starting this release, container images publish to `ghcr.io/certctl-io/certctl-server` and `ghcr.io/certctl-io/certctl-agent`. Existing pulls from `ghcr.io/shankar0123/certctl-{server,agent}:` continue to work for previously-published tags (the registry never deletes images), but the `:latest` tag at the old path stops moving forward at this release. Update your `docker pull` paths, `docker-compose.yml` `image:` keys, or Helm `image.repository` values to receive future updates. Old `git clone` / `git push` / install-script / API URLs continue to redirect forever — only the container-registry path changed. + +This is the only operator-action-required change in v2.0.68. Other changes in this release are cosmetic URL refreshes after the GitHub-org transfer from `shankar0123/certctl` to `certctl-io/certctl` (HTTP redirects mean no other operator action is required) plus an internal contextcheck lint fix in the agent. Full commit list is on the [GitHub release page](https://github.com/certctl-io/certctl/releases/tag/v2.0.68). + +--- + certctl no longer maintains a hand-edited per-version changelog. Per-release notes are auto-generated from commit messages between consecutive tags.