jaredandClaude Opus 5 b6ea4a333e fix(cinny-deploy): queue a trigger that arrives mid-deploy instead of dropping it ...

lotus_deploy.sh took an flock and exited if a deploy was already running.
The poll loop only retargets origin/lotus while it is still waiting on
CI; a push that lands during npm ci / npm run build was silently never
deployed until the next unrelated push (cinny 81a6d9c9 — the MSC4515
call fix — passed CI but never reached the web root). A concurrent
trigger now leaves a .pending marker and the running deploy re-execs
itself once at the end, which re-fetches and re-gates on CI as usual.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA

2026-09-14 19:25:28 -04:00

..

config.json

fix(cinny): restore gifApiKey placeholder + redact leaked key from README

2026-07-08 00:56:47 -04:00

lotus_deploy.sh

fix(cinny-deploy): queue a trigger that arrives mid-deploy instead of dropping it

2026-09-14 19:25:28 -04:00

lotus-build.sh

fix(cinny): upstream-merge script pushes and hands off to CI instead of deploying

2026-09-13 00:44:44 -04:00

nginx.conf

chore(nginx): widen CSP frame-src to https: for room widgets (MSC1236)

2026-07-03 13:27:23 -04:00

upstream-check.sh

Switch Lotus Cinny from nightly dev to stable-release fork workflow

2026-05-13 16:57:35 -04:00