nurdotnet 720765ee77 ci(forgejo): guard deploy-stage — main code ≠ stage DB schema ... The stage DB is on Phase2c3_MsStrict (vat_rates dropped, etc.), but main still has Product.VatRateId / DbSet<VatRate> and friends — that code would blow up at startup against the current DB. The user's 'feat strict OtherSystem schema' commit (f7087e9) isn't present in main any more (looks like a rebase dropped it); the pre-built image with that SHA is still in the registry and that's what the stage is pinned to right now. Until main gets the matching code, deploy-stage should only fire on tag or manual dispatch — push-to-main still builds images, just doesn't roll the stage forward.		2026-04-23 17:10:04 +05:00
..
workflows	ci(forgejo): guard deploy-stage — main code ≠ stage DB schema	2026-04-23 17:10:04 +05:00