Update pipeline: staging first, smoke and visual checks, then production
Imported from GitHub issue El-SaMa/lamoi-waas#14 by @El-SaMa.
Tasks
- Windmill job (ops jobs go to Windmill): pull pinned versions from the catalogue → apply on staging → run checks → wait for operator OK or auto-promote rules → apply on production → run checks → rollback on failure.
- Checks: hardening (#4), fingerprint (#7), HTTP 200 on sample subsites, visual diff of the pattern page (#12) and 5 sample sites, a WooCommerce test checkout on staging, PHP error log empty.
- Snapshot before production update (El-SaMa/oma#175); one-command rollback.
- Release notes per update in the repo.
Acceptance criteria
- A dry-run update of one plugin goes through staging and production with all checks recorded.
Depends on
#12, #13, El-SaMa/oma#175.
Plan key W14. Epic: El-SaMa/lamoi-waas#25.