The backend service environment in docker-compose.selfhost.yml is an
explicit allowlist, and MULTICA_DINGTALK_SECRET_KEY was never on it:
Docker self-hosters who set the key in .env still got a disabled DingTalk
integration. Telegram had the same gap until #8611.
- Map MULTICA_DINGTALK_SECRET_KEY into the backend service.
- Document MULTICA_SLACK_SECRET_KEY and MULTICA_TELEGRAM_SECRET_KEY in
.env.example next to the other channel keys.
- Extend selfhost-config.test.sh: every key the server loads through
secretbox.LoadKey must be mapped in docker-compose.selfhost.yml and
listed in .env.example. The list comes from the server, not the docs,
because Telegram's key was missing from both.
- Run script-checks when server/cmd/server/router.go changes, where the
integration gates live, so a new channel key trips the guard in the PR
that adds it.
Co-authored-by: multica-agent <[email protected]>
* ci: scope validation and remove duplicate lifecycle runs
Co-authored-by: multica-agent <[email protected]>
* fix(migrations): renumber the Triage validate migration to 489
#8449 and #8436 merged minutes apart and both took 485, so
TestMigrationNumericPrefixesAreUnique fails on main and every PR branched from
it. #8436 owns 485-488, so the single validate file moves to 489.
Renaming an applied migration makes databases that already recorded
485_issue_triage_state_validate run it once more under the new version string.
That is safe here: VALIDATE CONSTRAINT on an already-validated constraint is a
no-op, verified against PostgreSQL 17.
Co-authored-by: multica-agent <[email protected]>
(cherry picked from commit 09140a04aea06e8ca1cf008433cad3600d851cef)
* fix(ci): gate installers and reuse frontend quality setup
Co-authored-by: multica-agent <[email protected]>
* docs(ci): remove redundant CI overview
Co-authored-by: multica-agent <[email protected]>
* refactor(ci): remove unused output and duplicate test fixtures
Co-authored-by: multica-agent <[email protected]>
---------
Co-authored-by: Lambda <[email protected]>
Co-authored-by: multica-agent <[email protected]>
Co-authored-by: J <[email protected]>
