fix: publish latest tag for the newest stable release - #38
Merged
Conversation
The owncloud/ocis repository on Docker Hub has a latest tag that is now 5 months stale — it predates this repo's CI, which only publishes version tags (X.Y.Z, X.Y, X, <version>-YYYYMMDD). Anyone pulling owncloud/ocis:latest is silently stuck on an old release without security or bug fixes. Add latest to the extra-tags of the newest stable matrix entry (8.2.0) so every build — including the weekly scheduled rebuild that picks up Alpine security patches — repoints latest at the current stable image. A comment in the matrix marks that latest must move along with the newest stable entry on future version bumps. Also refresh the stale README Supported Tags table (it still listed 8.1.0 as latest stable and 8.0.5) to match the actual build matrix, document the latest tag, and bump the quick-start example to 8.2.0. The README is synced to Docker Hub as the image description. Signed-off-by: Lukas Hirt <info@hirt.cz>
DeepDiver1975
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
owncloud/ocisrepository on Docker Hub has alatesttag that is now 5 months stale — it predates this repo's CI, which only publishes version tags (X.Y.Z,X.Y,X,<version>-YYYYMMDD). The rolling repo gets itslatestfromrolling.yml, but the stable image never repoints it. Anyone pullingowncloud/ocis:latestis silently stuck on an old release without security or bug fixes.Fix
latestto theextra-tagsof the newest stable matrix entry (8.2.0) inmain.yml, so every build — including the weekly scheduled rebuild that picks up Alpine security patches — repointslatestat the current stable image.latestmust move along with the newest stable entry on future version bumps.latesttag with a pin-a-version recommendation, and bump the quick-start example to 8.2.0. The README is synced to Docker Hub as the image description.