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

chore: upgrade to 0.4.0+v1.19.0 #5

Open
autonomic-bot wants to merge 0 commits from upgrade-0.4.0+v1.19.0 into main
pull from: upgrade-0.4.0+v1.19.0
merge into: recipe-maintainers:main
Conversation 2 Commits - Files Changed -
autonomic-bot commented 2026-06-09 01:32:52 +00:00
Owner
Copy Link

Upgrade lasuite-meet to 0.4.0+v1.19.0.

Single commit, only compose.yml:

  • meet-frontend / meet-backend / celery: v1.16.0 → v1.19.0
  • redis: 8.6.3 → 8.6.4
  • version label: 0.3.0+v1.16.0 → 0.4.0+v1.19.0

Replaces #3, which had drifted out of sync with upstream main (it re-introduced renovate.json, README docs, and the .env.sample TURN fix that are already merged upstream). This PR branches directly off current upstream main so the diff contains only the version bump.

cc @trav @notplants

Upgrade lasuite-meet to `0.4.0+v1.19.0`. Single commit, only `compose.yml`: - meet-frontend / meet-backend / celery: `v1.16.0` → `v1.19.0` - redis: `8.6.3` → `8.6.4` - version label: `0.3.0+v1.16.0` → `0.4.0+v1.19.0` Replaces #3, which had drifted out of sync with upstream main (it re-introduced `renovate.json`, README docs, and the `.env.sample` TURN fix that are already merged upstream). This PR branches directly off current upstream main so the diff contains only the version bump. cc @trav @notplants
autonomic-bot added 1 commit 2026-06-09 01:32:53 +00:00
chore: upgrade to 0.4.0+v1.19.0
All checks were successful
cc-ci/testme cc-ci: success
Details
e8776e967a
autonomic-bot requested review from trav 2026-06-09 01:32:53 +00:00
autonomic-bot requested review from notplants 2026-06-09 01:32:53 +00:00
autonomic-bot commented 2026-06-09 01:33:15 +00:00
Author
Owner
Copy Link

!testme

!testme
autonomic-bot commented 2026-06-09 01:33:27 +00:00
Author
Owner
Copy Link

🌻 cc-ci — lasuite-meet @ e8776e96 ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `lasuite-meet` @ `e8776e96` ✅ **passed** [![cc-ci result card](https://ci.commoninternet.net/runs/204/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/204) [![level](https://ci.commoninternet.net/runs/204/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/204) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/204) · [dashboard](https://ci.commoninternet.net/)
All checks were successful
cc-ci/testme cc-ci: success
Details
This branch is already included in the target branch. There is nothing to merge.
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.0+v1.19.0:upgrade-0.4.0+v1.19.0
git checkout upgrade-0.4.0+v1.19.0
Sign in to join this conversation.
Reviewers
No Reviewers
notplants
trav
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#5
No description provided.
Delete Branch "upgrade-0.4.0+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?