v1.9.0

Added

• Traefik's timeouts on the HTTPS entry point can be set from .env.
  TRAEFIK_READ_TIMEOUT, TRAEFIK_WRITE_TIMEOUT and TRAEFIK_IDLE_TIMEOUT
  default to Traefik's own values (60s, 0s, 180s), so nothing changes unless
  you set them. Traefik reads its static configuration from one source, here
  the command in the compose file, and an override file can only replace that
  command whole; a variable is the way to tune it and keep taking updates.
  The same change was asked for in the Keycloak template, and every template in the fleet gets it at once.

v1.8.15

Changed

• owncloud/server:11.0.0 moved to owncloud/server:11.0.1. The freshness check reported the lag; the deploy job booted the stack on the new image before this landed.

Security

• owncloud/server:11.0.0 was rebuilt upstream; the pin moved from sha256:caaedd80d549… to sha256:f7c902c29ce2…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

What upstream changed

Read by fleet triage from the upstream release notes (or the commits between the tags) against this compose file, before the bump was applied.

Upstream changes 11.0.0 -> 11.0.1

Verdict: NEEDS ATTENTION - three security fixes affect preview generation and file previews for specific extensions; no companion-service version is named, so that clause of the verdict does not apply.

Breaking changes

• Preview rendering for a set of file extensions changes behaviour under "Security - Pin the Imagick coder for each preview provider" (#41834): "a file whose extension does not match its actual content no longer gets a preview: a JPEG saved as photo.tif is routed to the TIFF provider, pinned to the TIFF coder, and falls back to a media type icon where content sniffing previously rendered it... The affected extensions are ai, bw, eps, heic, heif, int, inta, pdf, ps, psd, rgb, rgba, sgi, tif and tiff. Of those providers only SGI and Heic are registered by default." Font files (otf, pfb, ttf) behave differently — mismatched files still get a thumbnail but drawn generically, and real .otf files gain previews they previously lacked.
• Appconfig public_/remote_ handling under "Security - Prevent path traversal via appconfig public_/remote_ keys" (#41856) changes API responses integrators may depend on: "the appconfig endpoints now refuse to read a core public_/remote_ key as well as to write one... Scripts which need a handler path should read it with occ config:app:get." Also: "Requesting a service which is not registered now answers 404 on both public.php and remote.php... remote.php sent a malformed status line; its refusals now answer 503."
• Federated address book sync is now restricted to the trusted server (#41869): "Requests which would leave the trusted server are now refused, and resource references which do not belong to it are skipped and logged." Any deployment relying on redirects or off-server resources in federation sync will see those requests fail (as intended).
• Share dialog behaviour changes: an "@"-containing search term is no longer always offered as a federated cloud id when it matches a local user/group exactly (#41807) — cosmetic/functional for search results, not a hard break.

Variables

• none named in the notes or in the compose/.env.example diff.

Data and dependencies

• none — no database, cache, or search-engine version requirement is mentioned in the notes, and the compose file's pins (mariadb 11.4, redis 7.4) are unaffected.
• Oracle-specific fixes (#41782, #41808) do not apply: this template runs OWNCLOUD_DB_TYPE: mysql against MariaDB, not Oracle.

Before applying

• If any startup hook, provisioning script, or automation reads a stored public_/remote_ handler path via the legacy core/ajax/appconfig endpoint or GET /settings/appconfig/core/..., switch it to occ config:app:get before upgrading — the old read path is now refused.
• If federation is configured, confirm the trusted server does not rely on redirects or serve resources from elsewhere; those paths will now be blocked and logged.
• No database migration, backup step, or config edit is otherwise called for by the notes.

Notes read

• v11.0.1 (2026-09-25) — CHANGELOG.md section "Changelog for ownCloud Core 11.0.1", full details read.
• v11.0.0 (2026-07-30) — included for context (partially, truncated by source length) since it is the version being moved from, but the review scope is the 11.0.0 → 11.0.1 delta as reported in the 11.0.1 section above.
• The release-notes blocks for v11.0.1 and v10.16.5 themselves were empty (only date headers, no body text); the CHANGELOG.md content was used instead as it contains the actual detail.

v1.8.14

Fixed

• The restore scripts had never been run by CI, and could not have been.
  They carried the database name, user and backup directory as literals, found
  their containers with a name filter that misses them under any -p but the
  default. The data restore ran docker exec -it, which refuses to start
  without a terminal, and cleared the directory with rm -rf dir/*, which
  leaves every dotfile of the newer state in place. Both scripts now take every
  path, name and credential from the running backups container, accept the
  backup file name as an argument, stop the application while they work and
  start it again whatever happens, and CI runs them: a marker written after a
  backup must be gone once that backup is restored, for the database and for
  the application data.

Changed

• The freshness check has its own workflow, Pin Freshness. It ran inside Deployment Verification, whose badge is the one at the top of this README. Across the fleet, nine red runs in ten were a pin one version behind - which the fleet's triage moves within the day - and a reader cannot tell that from a stack that does not boot. The badge now says whether the stack boots. The job itself is unchanged.

v1.8.13

Security

• traefik:3.7 was rebuilt upstream; the pin moved from sha256:1c32e7c36820… to sha256:24841fe2de73…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.
• owncloud/server:11.0.0 was rebuilt upstream; the pin moved from sha256:a83733dbec33… to sha256:caaedd80d549…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.8.12

Security

• owncloud/server:11.0.0 was rebuilt upstream; the pin moved from sha256:7a93e772c15d… to sha256:a83733dbec33…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.8.11

Security

• redis:7.4 was rebuilt upstream; the pin moved from sha256:71da9275c5f3… to sha256:c6eabf748fc7…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.
• owncloud/server:11.0.0 was rebuilt upstream; the pin moved from sha256:da653be2cdbc… to sha256:7a93e772c15d…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.8.10

Security

• traefik:3.7 was rebuilt upstream; the pin moved from sha256:f86a2cab1b5c… to sha256:1c32e7c36820…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.
• mariadb:11.4 was rebuilt upstream; the pin moved from sha256:65ad406b90f2… to sha256:70cc072b29b4…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.8.9

Security

• owncloud/server:11.0.0 was rebuilt upstream; the pin moved from sha256:f23ea0e4ca83… to sha256:da653be2cdbc…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.8.8

Security

• mariadb:11.4 was rebuilt upstream; the pin moved from sha256:80494b981069… to sha256:65ad406b90f2…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.
• owncloud/server:11.0.0 was rebuilt upstream; the pin moved from sha256:8f5a434ea1d2… to sha256:f23ea0e4ca83…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

v1.8.7

Security

• owncloud/server:11.0.0 was rebuilt upstream; the pin moved from sha256:63fbab9cf49d… to sha256:8f5a434ea1d2…. Same version, same tag, a rebuilt base image — the usual shape of a security fix in a base layer.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.