ersatztv

New `migrations` job in docker-build.yml runs on every push/PR and, per provider:
- `dotnet ef migrations has-pending-model-changes` — fails on model drift (an entity
  changed without a matching migration).
- `dotnet ef database update` against a fresh empty DB — applies all migrations,
  catching broken/un-orderable ones.

SQLite (the prod provider) uses a throwaway file; MySql uses ServerVersion.AutoDetect
(connects at config time), so the job runs a `services: mysql:8.4` container (the
act_runner uses Docker execution on network downloadswarm, so the service is reachable
as `mysql:3306`). Independent gate for now (not a `needs:` of the image build) so the
MySql-service dependency can't block image builds until proven stable.

Validated both providers locally against real DBs: SQLite 787 migrations -> 139 tables;
MySql 8.4 305 migrations -> 137 tables; both model-drift checks clean.

Docs: ci-cd.md "Migration integrity" (dual-provider discipline, EF CLI pattern, the
non-transactional caveat) + CLAUDE.md convention.

Refs #13

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-27 10:58:41 +02:00

channels.md

Add architecture docs and fork maintenance strategy (#6 )

2026-03-17 22:42:07 +01:00

ci-cd.md

ci: EF migration integrity checks for SQLite + MySql (#13 )

2026-06-27 10:58:41 +02:00

fork-strategy.md

Add architecture docs and fork maintenance strategy (#6 )

2026-03-17 22:42:07 +01:00

m3u-xmltv.md

docs: confirm root cause of M3U logo issue (#1 ), document URL-generation architecture

2026-06-26 22:02:19 +02:00