Files
cc-ci-orchestrator/cc-ci-plan/used-recipes.md
T
autonomic-bot 74a57d37b3 recipes: enroll wordpress as weekly-maintained
used-recipes.md: wordpress weekly row. upstream/wordpress.md: registry entry
(wordpress official image + mariadb; install-wizard/XML-RPC test notes).
Mirror recipe-maintainers/wordpress created + synced (adcd0e9f). Test suite +
bridge enrollment: cc-ci PR #14 (verify + bridge deploy deferred until the
in-flight /upgrade-all completes).
2026-08-03 21:06:20 +00:00

38 lines
1.4 KiB
Markdown

# Used recipes — the canonical inventory of every recipe cc-ci deploys/tests
Format: `<recipe> <tier> [note]` — one row per recipe. Tier:
- **`weekly`** — cc-ci maintains it: included in the weekly `/upgrade-all` survey **and** upgrade
(an upgrade PR is opened when a new upstream version exists).
- **`external`** — cc-ci **uses/tests** it (it's deployed + has `tests/<recipe>/`), but **someone
else maintains/upgrades it**, so it is **excluded from the weekly upgrade** — no upgrade PR is
opened for it. It still runs in CI like any other recipe; we just don't version-bump it.
`/upgrade-all` reads this file and upgrades only the `weekly` rows (see the skill §1). This list is
the source of truth for "what recipes do we use" — keep it in sync when recipes are enrolled/retired.
```
bluesky-pds weekly
cryptpad weekly
custom-html weekly
custom-html-tiny weekly
discourse weekly
drone weekly
ghost weekly
gitea weekly
hedgedoc weekly
immich weekly
keycloak weekly
lasuite-docs weekly
lasuite-drive weekly
lasuite-meet weekly
mailu weekly
matrix-synapse weekly
mattermost-lts weekly
mumble weekly
n8n weekly
plausible weekly
uptime-kuma external # maintained elsewhere — used/tested by cc-ci but NOT weekly-upgraded
wordpress weekly
```