LotusGuild/cinny
3
0
Fork 0
Code Issues 122 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

docs: deploy trigger queueing + how to verify a deploy actually landed
CI / Build & Quality Checks (push) Successful in 1m30s
Details
CI / Docker image build & smoke test (push) Skipped
Details
CI / Secret scan (gitleaks) (push) Successful in 10s
Details
CI / Trigger Desktop Build (push) Successful in 7s
Details
CI / Playwright smoke (e2e) (push) Successful in 2m16s
Details

Browse Source 
Re-fires the lotus-deploy webhook for 81a6d9c9 (MSC4515 call fix), whose
trigger was dropped by the deploy lock.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA
This commit is contained in:
jared
2026-09-14 19:25:45 -04:00
co-authored by Claude Opus 5
parent 81a6d9c9ed
commit 62f214f441
2 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
LOTUS_TESTING.md
+4
View File
@@ -847,3 +847,7 @@ Implemented and gate-green; confirm each per `LOTUS_TESTING.md`, then delete the
**Verified working in live testing (2026-06):** A2, B1–B4, C1, C3, D (mic/camera/deafen/screenshare/fullscreen/more-menu/PiP). Denoise quality in D is still poor — tracked under the denoise project, not a regression.
---
### Green CI but the fix isn't live?
`curl -s https://chat.lotusguild.org/index.html | grep -o 'assets/index-[^"]*\.js'` gives the deployed entry chunk; grep it for a string unique to your change (`curl -s https://chat.lotusguild.org/<that path> | grep -c <string>`). If it's 0 after ~15 min, the deploy trigger was lost — push again (any commit) to re-fire the `lotus-deploy` webhook. The deploy log lives at `/var/log/lotus-deploy.log` on LXC 106.