Extends this upgrade PR with the meet monorepo bump to v1.35.0, livekit to v1.13.10, and
nginx to 1.31.7. This PR does not touch the coop-cloud.${STACK_NAME}.version label.
None required. v1.35.0 adds new optional settings (USER_ACCESS_TOKEN_* default disabled; EXCHANGE_ACCESS_TOKEN_THROTTLE_RATES, EMAIL_TIMEOUT defaulted) and a non-destructive migration
(core.0025_application_client_secret_sha256, a nullable column — runs automatically on boot). No
removed setting (APPLICATION_CLIENT_SECRET_LENGTH, LOBBY_COOKIE_NAME) is used by this recipe.
nginx 1.31.7 is a security release (5 CVEs).
Advisory scan
6 CVEs fixed in this window: 5 nginx (1.31.7 security release: CVE-2026-15176, CVE-2026-93479,
CVE-2026-95101, CVE-2026-97629, CVE-2026-97205) + CVE-2026-4775 (tiff, fixed in the meet frontend
v1.35.0). The deterministic scan flagged incomplete github-advisory sources for the non-moving
sidecars (redis/pgautoupgrade/nginx) — the nginx CVEs were recovered from the vendor CHANGES URL.
Recommended publish (after merge)
abra recipe release lasuite-meet -y
Semver reasoning: new features + security fixes, no breaking config change → minor
(0.7.0+v1.31.0 → 0.8.0+v1.35.0).
Deployed and inspected directly on cc-ci under a dev- domain with --chaos before opening this
PR: all 7 services 1/1, migrations applied (incl. core.0025/core.0026), backend + __heartbeat__
serving 200, livekit 1.13.10, nginx 1.31.7. The dev- deploy was torn down after.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
## Recipe upgrade: lasuite-meet v1.34.0 → v1.35.0 (+ livekit v1.13.10, nginx 1.31.7)
Extends this upgrade PR with the meet monorepo bump to **v1.35.0**, livekit to **v1.13.10**, and
nginx to **1.31.7**. This PR does **not** touch the `coop-cloud.${STACK_NAME}.version` label.
| service | image | current | new |
|---------|-------|---------|-----|
| app | lasuite/meet-frontend | v1.34.0 | **v1.35.0** |
| backend | lasuite/meet-backend | v1.34.0 | **v1.35.0** |
| celery | lasuite/meet-backend | v1.34.0 | **v1.35.0** |
| livekit | livekit/livekit-server | v1.13.9 | **v1.13.10** |
| web | nginx | 1.31.6 | **1.31.7** |
| redis | redis | 8.10.2 | unchanged (latest) |
| db | pgautoupgrade/pgautoupgrade | 18-debian | unchanged (latest) |
**Upstream release notes:** app/backend/celery meet v1.34.0→v1.35.0: https://github.com/suitenumerique/meet/releases/tag/v1.35.0
**Upstream release notes:** livekit v1.13.9→v1.13.10: https://github.com/livekit/livekit/releases/tag/v1.13.10
**Upstream release notes:** web nginx 1.31.6→1.31.7: https://nginx.org/en/CHANGES
### Operator Action Required
None required. v1.35.0 adds new optional settings (`USER_ACCESS_TOKEN_*` default disabled;
`EXCHANGE_ACCESS_TOKEN_THROTTLE_RATES`, `EMAIL_TIMEOUT` defaulted) and a non-destructive migration
(`core.0025_application_client_secret_sha256`, a nullable column — runs automatically on boot). No
removed setting (`APPLICATION_CLIENT_SECRET_LENGTH`, `LOBBY_COOKIE_NAME`) is used by this recipe.
nginx 1.31.7 is a security release (5 CVEs).
### Advisory scan
6 CVEs fixed in this window: 5 nginx (1.31.7 security release: CVE-2026-15176, CVE-2026-93479,
CVE-2026-95101, CVE-2026-97629, CVE-2026-97205) + CVE-2026-4775 (`tiff`, fixed in the meet frontend
v1.35.0). The deterministic scan flagged incomplete github-advisory sources for the non-moving
sidecars (redis/pgautoupgrade/nginx) — the nginx CVEs were recovered from the vendor `CHANGES` URL.
### Recommended publish (after merge)
`abra recipe release lasuite-meet -y`
Semver reasoning: new features + security fixes, no breaking config change → minor
(`0.7.0+v1.31.0` → `0.8.0+v1.35.0`).
_Deployed and inspected directly on cc-ci under a `dev-` domain with `--chaos` before opening this
PR: all 7 services 1/1, migrations applied (incl. `core.0025`/`core.0026`), backend + `__heartbeat__`
serving 200, livekit 1.13.10, nginx 1.31.7. The `dev-` deploy was torn down after._
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
autonomic-bot
changed title from chore: upgrade lasuite/meet to v1.34.0 to chore: upgrade lasuite/meet to v1.35.0, livekit to v1.13.10, nginx to 1.31.72026-10-16 02:52:17 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Recipe upgrade: lasuite-meet v1.34.0 → v1.35.0 (+ livekit v1.13.10, nginx 1.31.7)
Extends this upgrade PR with the meet monorepo bump to v1.35.0, livekit to v1.13.10, and
nginx to 1.31.7. This PR does not touch the
coop-cloud.${STACK_NAME}.versionlabel.Upstream release notes: app/backend/celery meet v1.34.0→v1.35.0: https://github.com/suitenumerique/meet/releases/tag/v1.35.0
Upstream release notes: livekit v1.13.9→v1.13.10: https://github.com/livekit/livekit/releases/tag/v1.13.10
Upstream release notes: web nginx 1.31.6→1.31.7: https://nginx.org/en/CHANGES
Operator Action Required
None required. v1.35.0 adds new optional settings (
USER_ACCESS_TOKEN_*default disabled;EXCHANGE_ACCESS_TOKEN_THROTTLE_RATES,EMAIL_TIMEOUTdefaulted) and a non-destructive migration(
core.0025_application_client_secret_sha256, a nullable column — runs automatically on boot). Noremoved setting (
APPLICATION_CLIENT_SECRET_LENGTH,LOBBY_COOKIE_NAME) is used by this recipe.nginx 1.31.7 is a security release (5 CVEs).
Advisory scan
6 CVEs fixed in this window: 5 nginx (1.31.7 security release: CVE-2026-15176, CVE-2026-93479,
CVE-2026-95101, CVE-2026-97629, CVE-2026-97205) + CVE-2026-4775 (
tiff, fixed in the meet frontendv1.35.0). The deterministic scan flagged incomplete github-advisory sources for the non-moving
sidecars (redis/pgautoupgrade/nginx) — the nginx CVEs were recovered from the vendor
CHANGESURL.Recommended publish (after merge)
abra recipe release lasuite-meet -ySemver reasoning: new features + security fixes, no breaking config change → minor
(
0.7.0+v1.31.0→0.8.0+v1.35.0).Deployed and inspected directly on cc-ci under a
dev-domain with--chaosbefore opening thisPR: all 7 services 1/1, migrations applied (incl.
core.0025/core.0026), backend +__heartbeat__serving 200, livekit 1.13.10, nginx 1.31.7. The
dev-deploy was torn down after.Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
lasuite-meet@6cb491b7✅ passedfull logs · dashboard
chore: upgrade redis to 8.10.2to chore: upgrade lasuite/meet to v1.32.1!testme
🌻 cc-ci —
lasuite-meet@547536dc✅ passedfull logs · dashboard
chore: upgrade lasuite/meet to v1.32.1to chore: upgrade lasuite/meet to v1.33.0!testme
🌻 cc-ci —
lasuite-meet@071101c1✅ passedfull logs · dashboard
chore: upgrade lasuite/meet to v1.33.0to chore: upgrade lasuite/meet to v1.34.0!testme
🌻 cc-ci —
lasuite-meet@e474ca54✅ passedfull logs · dashboard
chore: upgrade lasuite/meet to v1.34.0to chore: upgrade lasuite/meet to v1.35.0, livekit to v1.13.10, nginx to 1.31.7!testme
🌻 cc-ci —
lasuite-meet@0d8e0d69✅ passedfull logs · dashboard