5 Commits

Include renames

Author	SHA1	Message	Date
TudorandClaude Opus 5	0c901cd0d1	feat(ci): gate promotion on the image set that actually passed E2E ... Staging health polling asked only whether something answered HTTP 200 at the base URL. It could not tell the new deployment from the old one, so journeys could pass against the previous release, and concurrent merges could move the staging tags underneath a run in flight. Each staging run now mints a build ID and stamps all three images with the commit and that ID, as labels and — for frontend and backend — as a build-time JSON file that environment overrides cannot rewrite. /release.json reports both identities uncached, and scripts/ci/release.py polls for the expected pair before and after the journeys. Only then are the captured build digests tagged verified-<sha>. Promotion resolves those verified tags to immutable digests, revalidates their labels, and refuses a mixed or incomplete set before any :prod tag moves. The whole staging workflow shares one concurrency group with cancellation disabled, so releases serialise. The scripts are stdlib-only and unit-tested against mocked registry and HTTP behaviour; PR checks now run the pipeline and CI suites too. The runbook records what this cannot prove locally, and that the first rollout needs a commit built by this workflow. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-15 10:17:50 +01:00
Tudor Sitaru	cacbeeb068	fixing backend image	2026-04-01 15:05:21 +01:00
Tudor Sitaru	52fbade30c	Introducing Postgresql for persistance	2026-01-06 17:15:43 +00:00
Tudor Sitaru	54e4bc2e77	Refactoring and bug fixes	2026-01-06 16:30:32 +00:00
Tudor Sitaru	c65eb1a00f	initial commit	2026-01-06 13:52:00 +00:00