recipe-maintainers/lasuite-meet
0
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

chore: upgrade to 0.4.1+v1.19.0 #6

Open
autonomic-bot wants to merge 1 commits from upgrade-0.4.1+v1.19.0 into main
pull from: upgrade-0.4.1+v1.19.0
merge into: recipe-maintainers:main
Conversation 0 Commits 1 Files Changed 1 +3 -3
autonomic-bot commented 2026-06-09 23:16:19 +00:00
Owner
Copy Link

Upgrade lasuite-meet from 0.4.0+v1.19.0 to 0.4.1+v1.19.0.

Infrastructure image bumps only — the primary Meet app stays at v1.19.0.

Image tag changes

Service Old tag New tag
livekit (livekit/livekit-server) v1.12.0 v1.13.1
redis 8.6.4 8.8.0

Operator action required

None. No new env vars, no config-template changes, no secrets/volumes/ports, no data migration. In-place container restart only. LiveKit v1.13.x dropped TURN-auth-without-TTL backwards compat, which this recipe already satisfied (v1.12.0 used TTL auth) — validated by the relay-only WebRTC test below.

Test results (test instance: lasuite-meet.cctest.autonomic.zone)

Test Result
tests/health_check.py ✓ PASS
tests/oidc_login.py ✓ PASS
tests/meeting_flow.py ✓ PASS
tests/webrtc-media.py ✓ PASS (5 audio frames end-to-end)
tests/webrtc-relay.py ✓ PASS (5 audio frames via TURN relay only)

All 7 services deployed healthy with the new tags (redis:8.8.0, livekit/livekit-server:v1.13.1).

Next steps (after PR review)

# 1. Review the PR on git.autonomic.zone (URL below)

# 2. Pull the PR branch to your local dev machine:
cd ~/.abra/recipes/lasuite-meet
git fetch git@git.autonomic.zone:recipe-maintainers/lasuite-meet.git upgrade-0.4.1+v1.19.0:upgrade-0.4.1+v1.19.0
git checkout upgrade-0.4.1+v1.19.0

# 3. Push to your upstream fork:
git push dev HEAD:upgrade-0.4.1+v1.19.0

# 4. Open a PR on upstream and merge it:
#    https://git.coopcloud.tech/coop-cloud/lasuite-meet/pulls

# 5. After the upstream PR merges, push the tag to publish the release:
git push dev 0.4.1+v1.19.0

cc @trav @notplants

Upgrade `lasuite-meet` from `0.4.0+v1.19.0` to `0.4.1+v1.19.0`. Infrastructure image bumps only — the primary Meet app stays at v1.19.0. ## Image tag changes | Service | Old tag | New tag | |---------|---------|---------| | livekit (livekit/livekit-server) | v1.12.0 | v1.13.1 | | redis | 8.6.4 | 8.8.0 | ## Operator action required None. No new env vars, no config-template changes, no secrets/volumes/ports, no data migration. In-place container restart only. LiveKit v1.13.x dropped TURN-auth-without-TTL backwards compat, which this recipe already satisfied (v1.12.0 used TTL auth) — validated by the relay-only WebRTC test below. ## Test results (test instance: lasuite-meet.cctest.autonomic.zone) | Test | Result | |------|--------| | `tests/health_check.py` | ✓ PASS | | `tests/oidc_login.py` | ✓ PASS | | `tests/meeting_flow.py` | ✓ PASS | | `tests/webrtc-media.py` | ✓ PASS (5 audio frames end-to-end) | | `tests/webrtc-relay.py` | ✓ PASS (5 audio frames via TURN relay only) | All 7 services deployed healthy with the new tags (redis:8.8.0, livekit/livekit-server:v1.13.1). ## Next steps (after PR review) ```bash # 1. Review the PR on git.autonomic.zone (URL below) # 2. Pull the PR branch to your local dev machine: cd ~/.abra/recipes/lasuite-meet git fetch git@git.autonomic.zone:recipe-maintainers/lasuite-meet.git upgrade-0.4.1+v1.19.0:upgrade-0.4.1+v1.19.0 git checkout upgrade-0.4.1+v1.19.0 # 3. Push to your upstream fork: git push dev HEAD:upgrade-0.4.1+v1.19.0 # 4. Open a PR on upstream and merge it: # https://git.coopcloud.tech/coop-cloud/lasuite-meet/pulls # 5. After the upstream PR merges, push the tag to publish the release: git push dev 0.4.1+v1.19.0 ``` cc @trav @notplants
autonomic-bot added 1 commit 2026-06-09 23:16:20 +00:00
chore: upgrade to 0.4.1+v1.19.0 05cdafb5bb
autonomic-bot requested review from trav 2026-06-09 23:16:20 +00:00
autonomic-bot requested review from notplants 2026-06-09 23:16:20 +00:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin upgrade-0.4.1+v1.19.0:upgrade-0.4.1+v1.19.0
git checkout upgrade-0.4.1+v1.19.0
Sign in to join this conversation.
Reviewers
No Reviewers
trav
notplants
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
autonomic autonomic-bot notplants trav
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/lasuite-meet#6
No description provided.
Delete Branch "upgrade-0.4.1+v1.19.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?