Upgrade lasuite/meet (app + backend + celery — one monorepo tag) v1.30.0 → v1.31.0, on top of current main (0.6.0+v1.30.0).
Context: today's survey targeted v1.21.0 → v1.31.0 + sidecars (livekit v1.13.6, redis 8.10.1, nginx 1.31.5) from the pre-reconcile state (0.5.0+v1.21.0). Upstream has since merged our PR #9 (published 0.6.0+v1.30.0), which already delivered all of that except the final meet bump. This PR carries the remaining bump only — re-planned from the tip of upstream main; all sidecars verified still-newest per abra recipe upgrade.
Image tags
service
image
current (main)
new (this PR)
app
lasuite/meet-frontend
v1.30.0
v1.31.0
backend
lasuite/meet-backend
v1.30.0
v1.31.0
celery
lasuite/meet-backend
v1.30.0
v1.31.0
db
pgautoupgrade/pgautoupgrade
18-debian
unchanged
redis
redis
8.10.1
unchanged (newest)
livekit
livekit/livekit-server
v1.13.6
unchanged (newest; v1.31.0 pins LiveKit server v1.13.6)
Added: 1080p sending-resolution option (#1660); Traefik support via configurable media-auth url header (#1649, opt-in — not this recipe's nginx path); update room attributes from the external API; gunicorn request-duration logging; waiting-participant sorting by arrival time.
Changed: pins LiveKit server to v1.13.6 (recipe already there); frontend base image → 1.30.4-alpine3.24.
None for this bump: no breaking changes, no new/renamed config used by this recipe, no manual migrations (Django migrations auto-run on backend boot).
Operators still on ≤0.6.0 should also read the v1.30.0 notes: the S3 storage-event recording webhook was removed — recordings finalize solely via LiveKit's egress_ended webhook (this recipe's livekit-server.yaml.tmpl already configures it).
Recommended release
This PR does not bump the version label (release is the operator's final step). After merge, publish with:
abra recipe release lasuite-meet -y
(minor bump: new features, no breaking changes → 0.7.0+v1.31.0 from 0.6.0+v1.30.0)
Verification
Direct deploy of this exact tree on cc-ci (--chaos, dedicated dev domain): all 7 services converged 1/1; Django migrations applied cleanly (full train incl. core.0022); gunicorn listening; celery connected to redis; livekit v1.13.6 + TURN started; SPA and livekit domains both HTTP 200 via the gateway. Dev deploy torn down afterwards (0 stacks/volumes/services).
!testme (cc-ci full lifecycle CI: install + backup/restore + upgrade tiers) — run below; results in this PR.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
Upgrade lasuite/meet (app + backend + celery — one monorepo tag) v1.30.0 → **v1.31.0**, on top of current main (`0.6.0+v1.30.0`).
**Context:** today's survey targeted `v1.21.0 → v1.31.0` + sidecars (livekit v1.13.6, redis 8.10.1, nginx 1.31.5) from the pre-reconcile state (`0.5.0+v1.21.0`). Upstream has since merged our PR #9 (published **0.6.0+v1.30.0**), which already delivered all of that except the final meet bump. This PR carries the **remaining** bump only — re-planned from the tip of upstream main; all sidecars verified still-newest per `abra recipe upgrade`.
## Image tags
| service | image | current (main) | new (this PR) |
|---|---|---|---|
| app | lasuite/meet-frontend | v1.30.0 | **v1.31.0** |
| backend | lasuite/meet-backend | v1.30.0 | **v1.31.0** |
| celery | lasuite/meet-backend | v1.30.0 | **v1.31.0** |
| db | pgautoupgrade/pgautoupgrade | 18-debian | unchanged |
| redis | redis | 8.10.1 | unchanged (newest) |
| livekit | livekit/livekit-server | v1.13.6 | unchanged (newest; v1.31.0 pins LiveKit server v1.13.6) |
| web | nginx | 1.31.5 | unchanged (newest) |
**Upstream release notes:** app (meet-frontend) v1.30.0→v1.31.0: https://github.com/suitenumerique/meet/releases/tag/v1.31.0
**Upstream release notes:** backend (meet-backend) v1.30.0→v1.31.0: https://github.com/suitenumerique/meet/releases/tag/v1.31.0
**Upstream release notes:** celery (meet-backend) v1.30.0→v1.31.0: https://github.com/suitenumerique/meet/releases/tag/v1.31.0
**Upstream release notes (context, already in main via 0.6.0):** meet v1.21.0→v1.30.0: https://github.com/suitenumerique/meet/releases/tag/v1.30.0 · livekit v1.13.1→v1.13.6: https://github.com/livekit/livekit/releases/tag/v1.13.6 · redis 8.8.0→8.10.1: https://github.com/redis/redis/releases · nginx 1.31.2→1.31.5: https://nginx.org/en/CHANGES
## What changed upstream (v1.31.0)
- Added: 1080p sending-resolution option (#1660); Traefik support via configurable media-auth url header (#1649, opt-in — not this recipe's nginx path); update room attributes from the external API; gunicorn request-duration logging; waiting-participant sorting by arrival time.
- Changed: pins LiveKit server to v1.13.6 (recipe already there); frontend base image → 1.30.4-alpine3.24.
- Fixed: printable-ASCII `sub` characters (#1673), sending-resolution persistence, lobby/presence Redis key-lookup bounding, UI fixes.
## Operator action required
- **None** for this bump: no breaking changes, no new/renamed config used by this recipe, no manual migrations (Django migrations auto-run on backend boot).
- Operators still on ≤0.6.0 should also read the v1.30.0 notes: the S3 storage-event recording webhook was removed — recordings finalize solely via LiveKit's `egress_ended` webhook (this recipe's `livekit-server.yaml.tmpl` already configures it).
## Recommended release
This PR does not bump the version label (release is the operator's final step). After merge, publish with:
`abra recipe release lasuite-meet -y`
(minor bump: new features, no breaking changes → `0.7.0+v1.31.0` from `0.6.0+v1.30.0`)
## Verification
- Direct deploy of this exact tree on cc-ci (`--chaos`, dedicated dev domain): all 7 services converged 1/1; Django migrations applied cleanly (full train incl. `core.0022`); gunicorn listening; celery connected to redis; livekit v1.13.6 + TURN started; SPA and livekit domains both HTTP 200 via the gateway. Dev deploy torn down afterwards (0 stacks/volumes/services).
- `!testme` (cc-ci full lifecycle CI: install + backup/restore + upgrade tiers) — run below; results in this PR.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
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.
Upgrade lasuite/meet (app + backend + celery — one monorepo tag) v1.30.0 → v1.31.0, on top of current main (
0.6.0+v1.30.0).Context: today's survey targeted
v1.21.0 → v1.31.0+ sidecars (livekit v1.13.6, redis 8.10.1, nginx 1.31.5) from the pre-reconcile state (0.5.0+v1.21.0). Upstream has since merged our PR #9 (published 0.6.0+v1.30.0), which already delivered all of that except the final meet bump. This PR carries the remaining bump only — re-planned from the tip of upstream main; all sidecars verified still-newest perabra recipe upgrade.Image tags
Upstream release notes: app (meet-frontend) v1.30.0→v1.31.0: https://github.com/suitenumerique/meet/releases/tag/v1.31.0
Upstream release notes: backend (meet-backend) v1.30.0→v1.31.0: https://github.com/suitenumerique/meet/releases/tag/v1.31.0
Upstream release notes: celery (meet-backend) v1.30.0→v1.31.0: https://github.com/suitenumerique/meet/releases/tag/v1.31.0
Upstream release notes (context, already in main via 0.6.0): meet v1.21.0→v1.30.0: https://github.com/suitenumerique/meet/releases/tag/v1.30.0 · livekit v1.13.1→v1.13.6: https://github.com/livekit/livekit/releases/tag/v1.13.6 · redis 8.8.0→8.10.1: https://github.com/redis/redis/releases · nginx 1.31.2→1.31.5: https://nginx.org/en/CHANGES
What changed upstream (v1.31.0)
subcharacters (#1673), sending-resolution persistence, lobby/presence Redis key-lookup bounding, UI fixes.Operator action required
egress_endedwebhook (this recipe'slivekit-server.yaml.tmplalready configures it).Recommended release
This PR does not bump the version label (release is the operator's final step). After merge, publish with:
abra recipe release lasuite-meet -y(minor bump: new features, no breaking changes →
0.7.0+v1.31.0from0.6.0+v1.30.0)Verification
--chaos, dedicated dev domain): all 7 services converged 1/1; Django migrations applied cleanly (full train incl.core.0022); gunicorn listening; celery connected to redis; livekit v1.13.6 + TURN started; SPA and livekit domains both HTTP 200 via the gateway. Dev deploy torn down afterwards (0 stacks/volumes/services).!testme(cc-ci full lifecycle CI: install + backup/restore + upgrade tiers) — run below; results in this PR.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@669cdf36✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.