Files
cc-ci-orchestrator/cc-ci-plan/used-recipes.md
T
autonomic-bot 929faeb055 config: drop plausible from weekly upgrade set (-> external)
Move plausible from weekly to external in used-recipes.md. cc-ci still
deploys/tests it (the recipe + tests stay enrolled, !testme bridge
unchanged), but it is no longer surveyed/upgraded by the weekly /upgrade-all
run — maintained elsewhere, like uptime-kuma.

The open plausible PR #5 (clickhouse 23.4.2.11 -> 23.4.6.25) from this week's
run stays open for the operator; no future weekly PRs will be opened for it.
2026-08-17 16:01:26 +00:00

38 lines
1.5 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 external # maintained elsewhere — used/tested by cc-ci but NOT weekly-upgraded
uptime-kuma external # maintained elsewhere — used/tested by cc-ci but NOT weekly-upgraded
wordpress weekly
```