6 Commits

Include renames

Author	SHA1	Message	Date
bermudalambandClaude Opus 5	2a20c0e05b	ci: manual workflow to build and publish the QA image (#25) ... Adds a workflow_dispatch job that builds a chosen ref, pushes it to the Gitea container registry as :qa plus a commit-sha tag, and emails when it is ready. It deliberately does not restart the QA stack — redeploying stays a human action in Portainer. The build runs against a Docker-in-Docker service rather than the NAS's Docker socket. Mounting the host socket into the runner would give every workflow on every branch root-equivalent control of the NAS, production included; pushing to a registry means the image does not need to survive in the build daemon. The QA stack now pulls that image instead of requiring a local build. The previous arrangement meant the image existed only if someone remembered to build it, which produced two confusing failures already: a Docker Hub "pull access denied" when the tag was missing, and a silent stale-image deploy when the build had not been rerun. Two runner capabilities cannot be verified from here — privileged service containers for dind, and a docker CLI in the runner image. The workflow checks both and fails with an explanation rather than a connection refused, and validates all five required secrets and variables up front rather than part-way through a build. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-17 19:10:04 -05:00
bermudalambandClaude Opus 5	ec63b9cdb0	fix: unset NODE_ENV in e2e job so devDependencies install ... npm treats NODE_ENV=production as --omit=dev, so `npm install` in the frontend-e2e job skipped typescript and the build died on `tsc: not found`. The same env var would have stripped vite and @playwright/test from the frontend install, and flipped the session cookie to Secure on a run served over plain http. The reported summarize crash was a symptom: the job aborted before Playwright ran, but Summarize is `if: always()` and threw ENOENT on the missing JSON, burying the real failure. Both summarize scripts now report the missing file and exit 0 -- the job still fails via its own step. Also split build from start, replaced `sleep 3` with a readiness poll against /api/config, and dump the backend log when e2e fails. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-15 08:56:25 -05:00
bermudalamb	483b1391a5	fix: use node-pg-migrate instead of deleted init.sql in e2e workflow	2026-08-14 16:18:20 -05:00
bermudalamb	2bff3a231f	ci: fix Postgres service port conflict in CI	2026-08-14 08:41:40 -05:00
bermudalamb	234330e482	Add CI test workflow with job summaries	2026-08-13 19:10:30 -05:00
bermudalamb	2adbf24b23	Add SonarQube CI workflow	2026-08-13 21:53:31 +00:00