From 4deca3e480a4567284606339065c704a1f839007 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 19 Jul 2026 18:50:16 +0000 Subject: [PATCH] docs: note that :latest can lag main by a few minutes after a release Came up debugging why a fresh pull still showed the old version in Settings: :latest legitimately rebuilds from whichever of the feature/release-bump pushes finishes last, so there's a brief window right after a release where it hasn't caught up yet. --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 453439a..8249231 100644 --- a/README.md +++ b/README.md @@ -162,6 +162,11 @@ the session cookie is marked `Secure`. - **Image tags:** `:latest` tracks `main`; version tags (`:1.0.0`, `:1.0`) are cut per release for pinning. If a host can't pull, the GHCR package may be private — make it public or `docker login ghcr.io`. +- **Pulled `:latest` but the version in Settings didn't change?** Give it a few minutes — + release-please's version-bump commit lands right behind the feature commit it releases, + and `:latest` rebuilds from whichever one finishes last. If it's still stale after that, + compare `docker inspect ghcr.io/strandedturtle/dockpull:latest --format '{{.Id}}'` + against the pinned `:X.Y.Z` tag for the version you expect — they should match. --- DISCLAIMER: This project was made using Claude