Skip to content

docs: note that :latest can lag main by a few minutes after a release #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
StrandedTurtle merged 1 commit into from
Jul 19, 2026
+5 −0
Merged

docs: note that :latest can lag main by a few minutes after a release #76

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down