M3-13 CI/CD Pipeline for Automated Deployments¶

Milestone: M3 — Issuing Functionality SOW Reference: NFR4 Requirement Clarity: ✅ Clear Dev Status: 🟡 Partially prototyped — build/lint/test pipeline exists; deploy step is a placeholder

Overview¶

Automated build, test and deployment pipeline so releases (v0.1 Beta onward) can ship reliably without manual steps.

Backend Tasks¶

Confirm .github/workflows/ci.yml (typecheck, lint, build, test, Docker build-check) stays green as the codebase grows
Replace the placeholder "deploy" step in .github/workflows/deploy.yml with a real deployment — still a literal placeholder as of 2026-08-17 (docker/metadata-action publishes images to GHCR, but nothing rolls them out). No longer blocked on deciding an AWS target, though: a working target now exists (single EC2 instance, docker-compose.server.yml + Caddy — see M4-01), deployed manually via SSH so far. This step just needs to automate what's currently done by hand (git pull + docker compose up --build on the instance), or be redesigned if a managed AWS service replaces this EC2 instance later.

Frontend Tasks¶

N/A

Dependencies¶

M4-01 — the AWS target decision this pipeline needs.
M3-14 — hardening steps may need to be part of the pipeline (dependency scanning, secrets checks).

Acceptance Criteria¶

CI/CD pipeline for automated deployments and automated testing packs in place (per SOW NFR4)

Existing Reference Material¶

REC_Platform_CICD_Deployment_Strategies.md (repo root — compares deployment options, doesn't commit to one yet)

Blockers & Risks¶

Blocking: AWS hosting target must be decided before this task can close.