feat(server): update 11.0.0-rc3 to 11.0.0 image from GitHub release tarball - #678
Merged
Conversation
…arball ownCloud 11.0.0 final is published, so point the v24.04 matrix entry at v11.0.0/owncloud-complete-20260730.tar.bz2 and rename the Trivy ignore folder to match the new tag. Two deliberate choices: - `latest` stays on 10.16.4. 11.0.0 is a new major, so an unpinned `docker pull owncloud/server` should not silently jump to it; 11.0.0 is opt-in via `owncloud/server:11.0.0`, as rc1-rc3 were. Moving `latest` (and adding `11.0`/`11`) is a separate, deliberate one-line change. - The smoke-test version assertion is enabled (`.versionstring`), where the RC entries had it disabled. The final release has a stable version string, so CI can now catch a mismatched tarball. Verified against the published tarballs: `occ status` reports versionstring 11.0.0. Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
jvillafanez
approved these changes
Jul 30, 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.
ownCloud 11.0.0 is
published, so point the
v24.04matrix entry at the final tarball.Changes
main.yml:11.0.0-rc3→11.0.0, tarball →v11.0.0/owncloud-complete-20260730.tar.bz2(verified: the exact URL theworkflow fetches returns
200).git mv v24.04/11.0.0-rc3/.trivyignore→v24.04/11.0.0/(100% rename).agents.md, andCHANGELOG.mdupdated to match.Two deliberate choices
lateststays on 10.16.4. 11.0.0 is a new major, so an unpinneddocker pull owncloud/servershouldn't silently jump to it — that would be abreaking change for anyone tracking
latest, and hard to unwind once images arepulled and cached. 11.0.0 is opt-in via
owncloud/server:11.0.0, exactly asrc1–rc3 were. Moving
latest(and adding11.0/11) is a separate, deliberateone-line change whenever you want it.
The smoke-test version assertion is now enabled (
smoke-version-jq: ".versionstring"), where the RC entries had it disabled (""). A final releasehas a stable version string, so CI can now catch a mismatched tarball. Verified
against the published tarballs — both the standard and complete builds report
versionstring: 11.0.0.Release verification (already done upstream)
The tarball this image builds from was verified end-to-end: GPG good signature
from the release key, all 57 G2 scopes ECDSA-verified against the real
root-g2chain, and a live install reportingintegrity:check-coreINTACTplus 15 apps INTACT.
One known cosmetic issue, filed as owncloud/core#41769, affects QA variants
only (
integrity:check-coreflags a test fixture) — the complete tarball usedhere is unaffected.