chore: upgrade to 1.37.0 (meet v1.36.3 -> v1.37.0) #13

Open
autonomic-bot wants to merge 1 commits from upgrade-1.37.0 into main
Owner

Upgrade lasuite-meet to meet v1.37.0 (frontend + backend + celery; the meet monorepo is versioned together).

service image current new
app lasuite/meet-frontend v1.36.3 v1.37.0
backend lasuite/meet-backend v1.36.3 v1.37.0
celery lasuite/meet-backend v1.36.3 v1.37.0
db pgautoupgrade/pgautoupgrade 18-debian 18-debian (unchanged)
redis redis 8.10.3 8.10.3 (unchanged)
livekit livekit/livekit-server v1.13.11 v1.13.11 (unchanged)
web nginx 1.31.8 1.31.8 (unchanged)

abra recipe upgrade found v1.37.0 for app/backend/celery and no newer tags for the sidecars.

Upstream release notes: app/backend/celery lasuite/meet v1.36.3→v1.37.0: https://github.com/suitenumerique/meet/releases/tag/v1.37.0
Full changelog: https://github.com/suitenumerique/meet/compare/v1.36.3...v1.37.0

Operator action required

  • Support form: the Crisp chat was removed and replaced by the La Suite support form. The support entry points stay hidden unless FRONTEND_SUPPORT sets widget_script_url, widget_api_url and widget_channel; any previous Crisp configuration is no longer used. This recipe never exposed Crisp/FRONTEND_SUPPORT, so no action is required to keep current behaviour — add those keys only if you want the new support form.
  • Search-engine hardening: non-root pages now ship <meta noindex> plus an X-Robots-Tag header and a robots.txt in the frontend image. The recipe's web service is a Co-op Cloud reverse proxy, so no recipe nginx change is needed.
  • Migrations: the backend still runs Django migrations on boot (migrate.sh); no breaking DB/volume/secret changes are called out in the v1.37.0 notes.

Verification

  • Direct --chaos deploy of this WIP on cc-ci (dev-lasuite-meet.ci.commoninternet.net, image tags v1.37.0) converged: 7/7 services 1/1, all Django migrations applied (migrate: done), gunicorn + celery ready, web served HTTP 200. Torn down cleanly (0 stacks / volumes / configs / secrets left).
  • !testme results on this PR are the authoritative CI verdict.

Operator publish (after the upstream PR merges)

The recipe version label is intentionally unchanged (0.8.2+v1.36.3). Run:

abra recipe release lasuite-meet -y

(Minor bump: new user-facing features — support form, noindex hardening, django-lasuite v1.0.0, arm64 asset builds.)

Nothing is merged — this PR awaits operator review.

Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.

cc @trav @notplants

Upgrade `lasuite-meet` to meet **v1.37.0** (frontend + backend + celery; the meet monorepo is versioned together). | service | image | current | new | |---------|-------|---------|-----| | app | lasuite/meet-frontend | v1.36.3 | **v1.37.0** | | backend | lasuite/meet-backend | v1.36.3 | **v1.37.0** | | celery | lasuite/meet-backend | v1.36.3 | **v1.37.0** | | db | pgautoupgrade/pgautoupgrade | 18-debian | 18-debian (unchanged) | | redis | redis | 8.10.3 | 8.10.3 (unchanged) | | livekit | livekit/livekit-server | v1.13.11 | v1.13.11 (unchanged) | | web | nginx | 1.31.8 | 1.31.8 (unchanged) | `abra recipe upgrade` found v1.37.0 for app/backend/celery and no newer tags for the sidecars. **Upstream release notes:** app/backend/celery lasuite/meet v1.36.3→v1.37.0: https://github.com/suitenumerique/meet/releases/tag/v1.37.0 Full changelog: https://github.com/suitenumerique/meet/compare/v1.36.3...v1.37.0 ## Operator action required - **Support form:** the Crisp chat was removed and replaced by the La Suite support form. The support entry points stay hidden unless `FRONTEND_SUPPORT` sets `widget_script_url`, `widget_api_url` **and** `widget_channel`; any previous Crisp configuration is no longer used. This recipe never exposed Crisp/`FRONTEND_SUPPORT`, so **no action is required** to keep current behaviour — add those keys only if you want the new support form. - **Search-engine hardening:** non-root pages now ship `<meta noindex>` plus an `X-Robots-Tag` header and a `robots.txt` in the frontend image. The recipe's `web` service is a Co-op Cloud reverse proxy, so no recipe nginx change is needed. - **Migrations:** the backend still runs Django migrations on boot (`migrate.sh`); no breaking DB/volume/secret changes are called out in the v1.37.0 notes. ## Verification - Direct `--chaos` deploy of this WIP on cc-ci (`dev-lasuite-meet.ci.commoninternet.net`, image tags v1.37.0) converged: **7/7 services 1/1**, all Django migrations applied (`migrate: done`), gunicorn + celery ready, web served HTTP 200. Torn down cleanly (0 stacks / volumes / configs / secrets left). - `!testme` results on this PR are the authoritative CI verdict. ## Operator publish (after the upstream PR merges) The recipe version label is intentionally unchanged (`0.8.2+v1.36.3`). Run: ``` abra recipe release lasuite-meet -y ``` (Minor bump: new user-facing features — support form, noindex hardening, django-lasuite v1.0.0, arm64 asset builds.) Nothing is merged — this PR awaits operator review. 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 added 1 commit 2026-11-06 04:43:37 +00:00
autonomic-bot requested review from trav 2026-11-06 04:43:37 +00:00
autonomic-bot requested review from notplants 2026-11-06 04:43:37 +00:00
Author
Owner

!testme

!testme
Author
Owner

🌻 cc-ci — lasuite-meet @ 99be9d37 ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `lasuite-meet` @ `99be9d37` ✅ **passed** [![cc-ci result card](https://ci.autonomic.zone/runs/138/summary.png)](https://drone.ci.autonomic.zone/recipe-maintainers/cc-ci/138) [![level](https://ci.autonomic.zone/runs/138/badge.svg)](https://drone.ci.autonomic.zone/recipe-maintainers/cc-ci/138) [full logs](https://drone.ci.autonomic.zone/recipe-maintainers/cc-ci/138) · [dashboard](https://ci.autonomic.zone/)
All checks were successful
cc-ci/testme cc-ci: success
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin upgrade-1.37.0:upgrade-1.37.0
git checkout upgrade-1.37.0
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/lasuite-meet#13