upstream(mattermost-lts): 2026-09-18 re-check — 11.7.11 newest ESR patch; PR #2 extended 11.7.10→11.7.11, GREEN (drone 1373); CVE-2026-13426 re-adjudicated FIXED (window count 14)

.opencode/skills/cctest-recipe-upstream/SKILL.md

@@ -50,6 +50,39 @@ not the test server — so it can run either way. Probe, then follow that branch
   4. Everything else in the canonical script (origin/dev remote setup, release recommendation,
      emitted next-steps) is identical.
 
+Every time the branch was prepared **here**, remember it exists only on this host — the
+operator's machine must fetch it first. Always emit this **step 0** before the push step
+(anonymous public fetch, no credentials needed):
+
+```
+  # 0. On a machine WITHOUT the branch pre-fetched, get it from the autonomic mirror
+  #    (fetch by URL — works regardless of what the local remotes are named):
+  cd <local checkout of the recipe>
+  git fetch https://git.autonomic.zone/recipe-maintainers/<recipe>.git +refs/pull/<PR_NUM>/head:refs/heads/<HEAD_REF>
+  git checkout <HEAD_REF>
+```
+
+If the operator's checkout does NOT yet have the mirror remote, emit once before the fetch:
+
+```
+  git remote add gitea https://git.autonomic.zone/recipe-maintainers/<recipe>.git
+```
+
 In both modes the final output is a set of commands for the operator to run on a machine **with
 push access to `git.coopcloud.tech`** — always print them, even when everything local is
 already prepared.
+
+**Verify the merge-base BEFORE rebasing — bases can be traps.** Upstream repos can
+carry a stray, divergent `main` ALONGSIDE the real `master` base branch. Rebase targets must be
+chosen by evidence: `git ls-remote origin | grep -E 'refs/heads/(main|master)$'`, then
+`git merge-base <head_ref> origin/<candidate>` — the correct base is the one where the upgrade
+branch's merge-base is its tip's parent (i.e. `<head_ref>` is already directly on that line —
+then NO cherry-pick is needed, the raw branch compares clean). Cherry-picking onto the wrong
+base produces the very messy 3-dot compare this guard exists to prevent (real case: gitea —
+first "rebase" landed on a stray `main` and had to be redone onto `master`).
+
+**Branch-name mismatch mirror vs upstream.** The mirror and upstream can use different base-branch
+names (gitea: mirror `main`, upstream `master`). When emitting step 3 (the post-merge release),
+NEVER hardcode `main` — derive the upstream default branch from the existing remotes (`git
+remote show origin` or `git ls-remote --symref origin HEAD`) and emit `git checkout <that>;
+git fetch origin; git merge --ff-only origin/<that>;` before `abra recipe release`.

cc-ci-plan/upstream/custom-html.md

@@ -9,6 +9,7 @@
 - nginx even-numbered minor versions (1.28.x, 1.30.x) are mainline; odd (1.27.x, 1.29.x) are stable. The recipe tracks mainline.
 - compose.git-pull.yml is an optional overlay for git-pull functionality; alpine/git version lives there.
 - compose.sftp.yml and compose.sso.yml are other optional overlays; linuxserver/openssh-server uses `latest` tag and is not version-pinned.
+- nginx 1.31.6 (15 Sep 2026) is a security patch release: CVE-2026-90439 (heap buffer overflow in a worker under certain configurations when using HTTP/3 with OpenSSL 3.5.0 and earlier). Change: QUIC transport parameters extension received in an SSL connection is now always ignored. Bugfixes: binary upgrade with control API socket + perl module; predicate-location evaluation error ignored; nested location lookup with regex/predicate locations; segfault reading config with `geo` … `ranges` + corrupted binary base file. None affect the custom-html static-file-serving use case (no HTTP/3/QUIC, no predicate locations, no perl, no `geo`).
 - Breaking change in nginx 1.31.0: HTTP/2 and HTTP/3 requests with Connection/Proxy-Connection/Keep-Alive/Transfer-Encoding/Upgrade/TE headers are now rejected.
 - Breaking change in nginx 1.29.7: keepalive in upstream block is enabled by default; proxy_http_version changed to 1.1; Connection proxy header no longer sent by default.
 - nginx 1.31.3 (15 Jul 2026) is a security patch release: CVE-2026-42533 (heap buffer overflow in `map` directive with regex matching / non-cacheable variable in string expression), CVE-2026-60005 (uninitialized memory access with unnamed regex captures + `slice` directive / background cache update → memory disclosure or worker crash), CVE-2026-56434 (use-after-free in `ngx_http_ssi_filter_module` processing crafted proxied backend response). Two non-security `Change`s: HTTP/2 response header/trailer size now limited by `proxy_buffer_size`/`grpc_buffer_size` in `ngx_http_proxy_v2_module`+`ngx_http_grpc_module`; external-entity loading disabled by default in `ngx_http_xslt_filter_module` (new `xml_external_entities` directive re-enables it). Plus bugfixes (HTTP/2 out-of-order pseudo-headers, flow control, Upgrade header in HTTP/2/3 responses). NONE of these changes affect the custom-html static-file-serving use case (no `map`, no `slice`/cache, no SSI, no xslt, no proxy_v2/grpc). No breaking config changes — no operator action required beyond the image pull.

cc-ci-plan/upstream/hedgedoc.md

@@ -7,7 +7,7 @@
 
 ## Standing notes
 - hedgedoc 1.11.0 (2026): 4 security CVEs fixed (HTML injection, YAML DoS, CSRF via Gist export, rate-limit bypass). No breaking changes, no migrations, no schema changes. Optional new env var `CMD_RATE_LIMIT_USING_CLOUDFLARE` only needed if running behind Cloudflare — not required for standard deployments.
-- pgautoupgrade: handles Postgres major-version upgrades automatically on container start. Bump ONE major at a time (16→17, then 17→18 on next cycle). The image tag is `<pg-major>-alpine`.
-- pgautoupgrade 18+ (deferred, learned 2026-09-11): PG 18 changes the data-directory layout (docker-library/postgres#1259; PGDATA → `/var/lib/postgresql/<MAJOR>/docker`) — this recipe mounts `postgres:/var/lib/postgresql/data` with no PGDATA, and per the pgautoupgrade README ("Error message when mounting data to /var/lib/postgresql/data on Postgres v18+") that needs a dedicated PGDATA/volume-mount change before bumping to 18, or you can get an empty instance instead of an upgraded one. 16→17 verified live on cc-ci 2026-09-11 (`Upgrade to PostgreSQL 17.11 complete.`, data survived).
+- pgautoupgrade: handles Postgres major-version upgrades automatically on container start; multi-major in ONE deploy works (16.15→18.6 verified live 2026-09-18 — pg_upgrade ran directly on the v16 files to 18.6, data survived). The image tag is `<pg-major>-alpine`.
+- pgautoupgrade 18+ (RESOLVED on PR #3, 2026-09-18): PG 18 changes the data-directory layout (docker-library/postgres#1259; PGDATA → `/var/lib/postgresql/<MAJOR>/docker`, `/var/lib/postgresql/data` becomes a symlink → mount error or EMPTY instance if the mount stays at .../data). The fix carried by PR #3: move the volume mount to `postgres:/var/lib/postgresql` (NO PGDATA env pin needed) — the entrypoint's `MOVING_TO_NEW_STRUCTURE` detects `/var/lib/postgresql/PG_VERSION`, upgrades, and moves data into `<MAJOR>/docker` automatically. Verified live on cc-ci 2026-09-18: `Upgrade to PostgreSQL 18.6 complete.`, pad data byte-identical, app green; 16→17 separately verified 2026-09-11 (`Upgrade to PostgreSQL 17.11 complete.`). Upstream coopcloud renovate PR #22 bumps the tag WITHOUT this mount fix — do not merge that alone.
 - hedgedoc 1.12.0 (2026-08): requires Node 20.17+ (app image bundles its own node — not recipe-relevant); webp uploads; some highlight.js languages removed/changed. No breaking changes or migrations for the recipe.
 - cc-ci tests use the sqlite backend (default compose.yml), not the postgresql compose override — so pgautoupgrade bumps do not affect CI test coverage (verify pg bumps via a direct --chaos deploy with the postgresql override instead).

cc-ci-plan/upstream/immich.md

@@ -68,6 +68,17 @@
   reject). Done in the 2026-09-11 upgrade (v3.1.0→v3.2.0, extending PR #4 from upstream main
   794560f; PR #4's pgvectors0.3.0/valkey-8e8d64b4 divergences superseded — DB realigned to
   immich's official combo, which upstream main itself chose 2026-08-07).
+- **immich-server v3.2.1 (2026-09-14) + v3.2.2 (2026-09-15) pins** (from `docker/docker-compose.yml`
+  @ the v3.2.2 tag): `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…` and
+  `valkey:9@sha256:70739f85ad…` — **BOTH identical to the recipe's v3.2.0-era pins** (DB and
+  redis stay put; live valkey `9` tag has drifted to `c123e371…` = 9.1.2 but immich's tested
+  pin `70739f85…` = 9.1.1 is kept per the 2026-07-17 precedent; live postgres tag digest
+  re-verified = the pin, not stale). `example.env` @ v3.2.2 byte-identical to v3.2.0. Both
+  releases are bug-fix-only (v3.2.1: sync connection-pool exhaustion, search modal, partner
+  assets on people page, person merge, server auto-VACUUM after TypeORM migrations; v3.2.2:
+  reassign-faces fix) — no breaking changes, no config additions, no operator action. Done in
+  the 2026-09-18 upgrade (v3.2.0→v3.2.2, app+ML only; fresh PR — PR #4 was closed when its
+  v3.2.0 content merged upstream as #19 / `1.11.0+v3.2.0`).
 - **2026-08-07 INFRA note: cc-ci runner's gitea clone-token is STALE (HTTP 401).** `!testme` build
   #1210 died at the recipe `git clone` step (~5s, before any deploy) with `could not read Username for
   'https://git.autonomic.zone'` — the runner's mounted gitea token `13e299f2…` is rejected (verified

cc-ci-plan/upstream/lasuite-docs.md

@@ -6,10 +6,10 @@
 | backend | lasuite/impress-backend | https://github.com/suitenumerique/docs | https://github.com/suitenumerique/docs/releases |
 | celery | lasuite/impress-backend | https://github.com/suitenumerique/docs | https://github.com/suitenumerique/docs/releases |
 | y-provider | lasuite/impress-y-provider | https://github.com/suitenumerique/docs | https://github.com/suitenumerique/docs/releases |
-| docspec | ghcr.io/docspecio/api | https://github.com/docspecIO/api | https://github.com/docspecIO/api/releases |
+| docspec | ghcr.io/docspec/api | https://github.com/docspec/docspec | https://github.com/docspec/docspec/releases |
 | db | pgautoupgrade/pgautoupgrade | https://github.com/pgautoupgrade/docker-pgautoupgrade | https://github.com/pgautoupgrade/docker-pgautoupgrade/releases |
 | redis | redis | https://github.com/redis/redis | https://hub.docker.com/_/redis/tags |
-| minio | minio/minio | https://github.com/minio/minio | https://github.com/minio/minio/releases |
+| minio | quay.io/minio/minio | https://github.com/minio/minio | https://github.com/minio/minio/releases |
 | web | nginx | https://github.com/nginx/nginx | https://nginx.org/en/CHANGES |
 
 ## Standing notes
@@ -36,3 +36,17 @@
 - redis sidecar (cache/broker for celery+backend): prefer the patch line (8.8.1 over 8.10.0) unless a
   feature is needed — 8.8.1 is a security patch (RedisBloom/TDigest RESTORE RCE); 8.10.0 is a minor
   with many new features.
+- **2026-09-18: docspec image switched with impress v5.7.0** (upstream PR suitenumerique/docs#2553):
+  `ghcr.io/docspecio/api:3.0.x` (Elixir, repo ARCHIVED) → `ghcr.io/docspec/api:1.21.4` (Rust rewrite,
+  github.com/docspec/docspec). New image listens on **3000** (was 4000): recipe sets
+  `DOCSPEC_API_URL=http://docspec:3000/conversion` and healthcheck `http://127.0.0.1:3000/health`
+  (path `/conversion` and the raw-body request contract unchanged).
+- ⚠️ When checking GHCR tags by script: the `/tags/list` endpoint CAPS AT 100 tags — a missing tag
+  there means nothing. Verify the **manifest** endpoint instead (e.g. `ghcr.io/docspec/api:1.21.4`
+  is absent from tags/list but pulls fine).
+- **2026-09-13ish: upstream #25 moved the minio pin to `quay.io/minio/minio`** (same
+  RELEASE.2025-09-07T16-13-09Z tag — manifest-verified pullable on quay; quay's own tags/list is
+  paginated and misleading, use manifest checks there too).
+- **v5.7.0 moved the favorites API endpoint to `/documents/favorites/`** — breaking only for
+  external API consumers, not the recipe/cc-ci tests (which use /authenticate/, /users/me/,
+  /documents/).

cc-ci-plan/upstream/lasuite-drive.md

@@ -9,8 +9,8 @@
 | db | pgautoupgrade/pgautoupgrade | https://github.com/pgautoupgrade/docker-pgautoupgrade | https://github.com/pgautoupgrade/docker-pgautoupgrade/releases |
 | redis | redis | https://github.com/redis/redis | https://github.com/redis/redis/releases |
 | mailcatcher | sj26/mailcatcher | https://github.com/sj26/mailcatcher | https://github.com/sj26/mailcatcher/releases |
-| minio | minio/minio | https://github.com/minio/minio | https://github.com/minio/minio/releases |
-| minio-createbuckets | minio/minio | https://github.com/minio/minio | https://github.com/minio/minio/releases |
+| minio | quay.io/minio/minio | https://github.com/minio/minio | https://github.com/minio/minio/releases |
+| minio-createbuckets | quay.io/minio/minio | https://github.com/minio/minio | https://github.com/minio/minio/releases |
 | collabora | collabora/code | https://github.com/CollaboraOnline/online | https://www.collaboraonline.com/release-notes/ (per-version: .../collabora-online-25-04-release-notes/) |
 | onlyoffice | onlyoffice/documentserver-de | https://github.com/ONLYOFFICE/DocumentServer | https://github.com/ONLYOFFICE/DocumentServer/blob/master/CHANGELOG.md |
 | web | nginx | https://github.com/nginx/nginx | https://nginx.org/en/CHANGES |
@@ -19,9 +19,12 @@
 - lasuite/drive-frontend and lasuite/drive-backend share the same version tag (drive monorepo).
 - minio and onlyoffice tags use non-semver formats; abra cannot auto-detect upgrades for them.
 - collabora/code uses a 5-part version scheme; abra cannot auto-detect upgrades for it.
-- minio: Docker Hub `minio/minio` `latest` is frozen at `RELEASE.2025-09-07T16-13-09Z` (the
-  `RELEASE.2025-10-15T17-29-55Z` GitHub security release is NOT on Docker Hub `minio/minio`).
-  Newer minio releases moved to the **AIStor** product line (`quay.io/minio/aistor/minio`).
-  A future minio bump requires a registry+product switch — operator decision, not a routine tag bump.
+- minio: Docker Hub `minio/minio` was **REMOVED** (verified 2026-09-18: Hub repo API 404, registry
+  manifest 401 on anonymous pull; last successful docker.io pull was the 2026-09-11 run). The same
+  release tag lives on **`quay.io/minio/minio`** (MinIO's official distribution channel) — recipe
+  pins switched there in lasuite-drive PR #7 (2026-09-18), same release `RELEASE.2025-09-07T16-13-09Z`,
+  mirroring the identical fix merged upstream for lasuite-docs ("fix: pull MinIO image from Quay",
+  PR #25, 2026-09-15). A future minio **version** bump still requires the AIStor product-line
+  decision — quay.io only re-hosts the frozen community line.
 - nginx 1.31.x (1.31.0, 1.31.1) contains multiple security CVE fixes; upgrade is recommended.
 - nginx 1.31.0 breaking change: HTTP/2 and HTTP/3 requests with Connection/Proxy-Connection/Keep-Alive/Transfer-Encoding/Upgrade headers are now rejected (affects proxied HTTP/2 backends).

cc-ci-plan/upstream/mattermost-lts.md

@@ -6,6 +6,23 @@
 | postgres | postgres                                  | https://github.com/postgres/postgres              | https://www.postgresql.org/docs/release/                          |
 
 ## Standing notes
+  - **2026-09-18 re-check** (Mattermost release-policy docs; GitHub release; Docker Hub; vendor
+    security feed): **11.7 ESR line UNCHANGED** — newest patch **11.7.11** (released 2026-09-15,
+    "Low to High severity level security fixes"; Docker Hub tag pushed 2026-09-15). v10.11 ESR
+    remains EXPIRED (2026-08-15); 10.11.24 sits on the dead line — do NOT target. This run
+    extended open PR #2 **11.7.10 → 11.7.11** (branch tip 5696f0b4). Direct `--chaos` deploy on
+    cc-ci exercised the full operator path (deploy at 10.11.22 → seed admin user via API →
+    upgrade to 11.7.11): schema migrations ran on boot, **seeded user data survived** (same
+    id/roles, login 200), ping 200 with x-version-id 11.7.11; `!testme` **GREEN**, drone 1373
+    (level 5: install/upgrade/backup/restore/custom all pass, clean teardown). Vendor feed: **6
+    server advisories fixed in 11.7.11** (MMSA-2026-00711 Low; -00761/-00763/-00764/-00765/-00773
+    Medium, all affecting 11.7.x <= 11.7.10; CVE ids pending 30-day disclosure, due 2026-10-15).
+    **CVE-2026-13426 re-adjudicated FIXED** for the 10.11.22 → 11.7.11 window (fresh GitHub
+    compare: fix commit 3321db82 is an ancestor of v11.7.11 — ahead/behind 0 — and diverged from
+    v10.11.22) → window CVE count **14** (13 deterministic + 1 adjudicated). postgres **15-alpine
+    HELD** (DB-major out of scope). Gotchas learned: `abra app new` RESETS the recipe checkout to
+    main (re-checkout the branch before a `--chaos` deploy), and `abra app new --domain` does NOT
+    write DOMAIN into the app .env (edit the .env + redeploy to fix traefik routing).
   - **2026-09-11 re-check** (Mattermost Server Releases docs; endoflife.date/api/mattermost.json;
     GitHub releases + module tags): **11.7 ESR line UNCHANGED** — newest patch still **11.7.10**
     (2026-08-26; no 11.7.11; v11.11.0 is still a GitHub **prerelease**, innovation). **10.11 ESR

cc-ci-plan/upstream/n8n.md

@@ -205,3 +205,37 @@
   2.36.0 Array.merge→mergeIntoObject + workflow-tags API migration; 2.37.0 "Any workflow" caller-policy
   deprecation + JSON content-type on decorator body routes + binary-data endpoint adapt; 2.39.0
   workflow-version endpoint deprecation. Recommended release: `-y` (feature minor).
+- 2.38.7 (2026-09-11, patch): 3 core fixes (MCP toolkit members on workers; consent-grant reuse;
+  trust the CA from GIT_SSL_CAINFO for source-control HTTPS remotes).
+- 2.39.3 (2026-09-11, Pre-release): 1 core fix (GIT_SSL_CAINFO trust — 2.38.7 backport).
+- 2.39.4 (2026-09-11, Pre-release): 1 core fix (sandbox npm install flags by provider).
+- 2.39.5 (2026-09-14, stable line): editor fix (revoke end-user credentials) + feature
+  (instance-report log streaming events).
+- 2.39.6 (2026-09-16, stable line): core fix (Gateway credits eligibility) + features (**v3
+  breaking-change rule for the storage-directory rename**; **warn on deprecated N8N_DB_PING_TIMEOUT
+  env var** — recipe does not set it).
+- 2.39.7 (2026-09-17, stable line; **`stable` tag points here** — the stable badge moved to the
+  2.39.x line): core breaking-change-detection resilience; editor numeric credential inputs.
+- 2.40.0 (2026-09-15, Pre-release, feature minor — large): Microsoft Dataverse core node; AI Agent
+  forced first-iteration tool calls; Git-based promotion model (selective promote, timestamped
+  branches, promotion entities/DTOs); **workflow publication service enabled by default**;
+  ephemeral sandboxes; agent episodic memory; ai_preference table; HTTP Request
+  PROPFIND/MKCOL/MOVE/COPY/REPORT; Grist OAuth2; MS Teams online-meeting/channel-message ops; v3
+  migration-report rules (storage-directory rename, preExecute) + "chat hub goes away" warning;
+  N8N_DB_PING_TIMEOUT deprecation warning; secret-redaction consolidation; queue-mode execution
+  timeout for stuck jobs; ~150 core/editor/node bugfixes. **No breaking compose/env/migration
+  changes; no N8N_* renames.**
+- 2.40.1 (2026-09-16, Pre-release): GitHub release body EMPTY (maintenance republish, no listed
+  changes).
+- 2.40.2 (2026-09-17, Pre-release): core breaking-change-detection resilience + editor numeric
+  credential inputs (the 2.39.7 pair on the 2.40 line). Docker Hub manifest verified active.
+- 2.40.3 (2026-09-18, Pre-release): core "repair data-encryption keys stored as the raw instance
+  key" + editor blank-workflow-preview fix. Published the morning of the 2026-09-18 run — newer
+  than the operator's snapshot (which named 2.40.2 as newest); NOT taken that run (operator's
+  explicit target 2.40.2), flagged in the plan/PR as a trivial follow-up bump.
+- 2026-09-18 run: PR #8 (branch upgrade-ef0dd56, at 2.39.2 since 2026-09-11, !testme GREEN then)
+  extended **2.38.4 → 2.40.2** on upstream main tip 0b436ec (still 3.5.0+2.38.4 — upstream has not
+  started the bump). Stable badge on 2.39.7; 2.40.x pre-release per precedent. Rolling upgrade
+  safe (sqlite, TypeORM auto-migrate). Operator flags unchanged (API-caller-level deprecations,
+  encryption-key rework informational, N8N_DB_PING_TIMEOUT warn-only, recipe doesn't set it).
+  2.40.3 exists (see above) — flagged, not taken. Recommended release: `-y`.

scripts/gen-cctest-skills.py

@@ -78,9 +78,42 @@ not the test server — so it can run either way. Probe, then follow that branch
   4. Everything else in the canonical script (origin/dev remote setup, release recommendation,
      emitted next-steps) is identical.
 
+Every time the branch was prepared **here**, remember it exists only on this host — the
+operator's machine must fetch it first. Always emit this **step 0** before the push step
+(anonymous public fetch, no credentials needed):
+
+```
+  # 0. On a machine WITHOUT the branch pre-fetched, get it from the autonomic mirror
+  #    (fetch by URL — works regardless of what the local remotes are named):
+  cd <local checkout of the recipe>
+  git fetch https://git.autonomic.zone/recipe-maintainers/<recipe>.git +refs/pull/<PR_NUM>/head:refs/heads/<HEAD_REF>
+  git checkout <HEAD_REF>
+```
+
+If the operator's checkout does NOT yet have the mirror remote, emit once before the fetch:
+
+```
+  git remote add gitea https://git.autonomic.zone/recipe-maintainers/<recipe>.git
+```
+
 In both modes the final output is a set of commands for the operator to run on a machine **with
 push access to `git.coopcloud.tech`** — always print them, even when everything local is
 already prepared.
+
+**Verify the merge-base BEFORE rebasing — bases can be traps.** Upstream repos can
+carry a stray, divergent `main` ALONGSIDE the real `master` base branch. Rebase targets must be
+chosen by evidence: `git ls-remote origin | grep -E 'refs/heads/(main|master)$'`, then
+`git merge-base <head_ref> origin/<candidate>` — the correct base is the one where the upgrade
+branch's merge-base is its tip's parent (i.e. `<head_ref>` is already directly on that line —
+then NO cherry-pick is needed, the raw branch compares clean). Cherry-picking onto the wrong
+base produces the very messy 3-dot compare this guard exists to prevent (real case: gitea —
+first "rebase" landed on a stray `main` and had to be redone onto `master`).
+
+**Branch-name mismatch mirror vs upstream.** The mirror and upstream can use different base-branch
+names (gitea: mirror `main`, upstream `master`). When emitting step 3 (the post-merge release),
+NEVER hardcode `main` — derive the upstream default branch from the existing remotes (`git
+remote show origin` or `git ls-remote --symref origin HEAD`) and emit `git checkout <that>;
+git fetch origin; git merge --ff-only origin/<that>;` before `abra recipe release`.
 """,
 }