Webstar/LibrePortal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(nextcloud,mastodon): track a moving stable line like every other app

Browse Source 
Both templates were stale in different ways, and the new tag enumeration
surfaced it: nextcloud sat on 31-fpm-alpine with 34 out, mastodon on
v4.2.0 with v4.6 out.

  nextcloud  31-fpm-alpine -> 34-fpm-alpine
  mastodon   v4.2.0        -> v4.6

The mastodon one was the real problem: v4.2.0 is an EXACT patch pin, so
it never moved at all — no security patches, ever. v4.6 is a moving
minor-line tag (the same shape as stalwart's v0.16), so auto-update now
delivers patches within the line.

Deliberately NOT floated to :latest or :stable. Both projects require
stepped upgrades — Nextcloud in particular refuses to skip a major — so
a tag that crosses majors on its own would break the app on a routine
container recreate. A major-pinned, patch-moving tag is the correct
shape here, not a limitation.

Verified against the registry: all three pinned apps now report nothing
newer, and each tag still moves (v0.16 2026-08-10, 34-fpm-alpine
2026-08-03, v4.6 2026-08-06).

Templates only, so this changes NEW installs. Existing installs keep
their tag and will now be told a newer line exists.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
librelad 2026-08-12 23:39:36 +01:00
parent 7334557706
commit 8a0c3641d0
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
containers/mastodon/docker-compose.yml
View File

@ -5,7 +5,7 @@ networks:
services:
mastodon-service: #LIBREPORTAL|SERVICE_TAG_1|mastodon-service
container_name: mastodon-service
image: tootsuite/mastodon:v4.2.0 #LIBREPORTAL|MASTODON_VERSION_TAG|v4.2.0
image: tootsuite/mastodon:v4.6 #LIBREPORTAL|MASTODON_VERSION_TAG|v4.6
ports:
- "PORTS_DATA_1" #LIBREPORTAL|PORTS_TAG_1|PORTS_DATA_1
- "PORTS_DATA_2" #LIBREPORTAL|PORTS_TAG_2|PORTS_DATA_2

2
containers/nextcloud/docker-compose.yml
View File

@ -9,7 +9,7 @@ services:
# automatically on first boot when the NEXTCLOUD_ADMIN_USER + MYSQL_* env
# vars are set, so no user wizard.
nextcloud-service: #LIBREPORTAL|SERVICE_TAG_1|nextcloud-service
image: nextcloud:31-fpm-alpine #LIBREPORTAL|NEXTCLOUD_VERSION_TAG|31-fpm-alpine
image: nextcloud:34-fpm-alpine #LIBREPORTAL|NEXTCLOUD_VERSION_TAG|34-fpm-alpine
container_name: nextcloud-service
environment:
- TZ=TIMEZONE_DATA #LIBREPORTAL|TIMEZONE_TAG|TIMEZONE_DATA