keep staging app code unchanged until candidate migrations succeed
run install/check/migrate in release candidate dir and promote only on success
document promotion gate in staging runbook
Why
Issue #130 reports gameplay smoke failure caused by schema mismatch after failed deploy. This change ensures failed deploys do not leave app code ahead of DB schema.
## Summary
- keep staging app code unchanged until candidate migrations succeed
- run install/check/migrate in release candidate dir and promote only on success
- document promotion gate in staging runbook
## Why
Issue #130 reports gameplay smoke failure caused by schema mismatch after failed deploy. This change ensures failed deploys do not leave app code ahead of DB schema.
Aligns with release-readiness tracking in #90.
Refs #130
Refs #90
Head SHA: e9104cdc449ef2bc7bb7338f5ad73c8c8d56f8fb
Problems:
No effective approval yet
Required for merge: all required checks green + at least one effective approval and no active request-changes.
Next step: push a new commit with fixes; integrator will re-evaluate on new head SHA.
Integrator blocker (severity: blocker)
- PR: #136
- Head SHA: `e9104cdc449ef2bc7bb7338f5ad73c8c8d56f8fb`
- Problems:
- No effective approval yet
- Required for merge: all required checks green + at least one effective approval and no active request-changes.
- Next step: push a new commit with fixes; integrator will re-evaluate on new head SHA.
Ingen blocker-fund i ændringerne til staging deploy-flowet.
CI status er grøn (push + pull_request).
Candidate→promote efter succesfuld migrate reducerer schema/code drift som tilsigtet.
Resultat: APPROVED (merge-klar fra review-perspektiv).
Review completed ✅
- Ingen blocker-fund i ændringerne til staging deploy-flowet.
- CI status er grøn (push + pull_request).
- Candidate→promote efter succesfuld migrate reducerer schema/code drift som tilsigtet.
Resultat: APPROVED (merge-klar fra review-perspektiv).
[integrator] PR ikke merge-klar endnu.\n\nSeverity: blocker\nSHA: e9104cdc449ef2bc7bb7338f5ad73c8c8d56f8fb\nBlokeringer:\n- check CI / test-and-quality (pull_request)=missing\n- check CI / test-and-quality (push)=missing\n\nKonkret fixforslag: adresser punkterne ovenfor, push nyt commit (nyt SHA), og afvent næste integrator-kørsel.
[integrator] PR ikke merge-klar endnu.\n\nSeverity: blocker\nSHA: `e9104cdc449ef2bc7bb7338f5ad73c8c8d56f8fb`\nBlokeringer:\n- check CI / test-and-quality (pull_request)=missing\n- check CI / test-and-quality (push)=missing\n\nKonkret fixforslag: adresser punkterne ovenfor, push nyt commit (nyt SHA), og afvent næste integrator-kørsel.
[scheduler][stagnation-gate] PR #136 er sat i stuck på uændret head SHA e9104cdc449ef2bc7bb7338f5ad73c8c8d56f8fb gennem >=2 cyklusser med gentagne blocker-kommentarer.
For at undgå retest-loop stoppes nye review/integrator-triggere for denne PR, indtil der foreligger nyt commit/head SHA.
Krav for genoptagelse: push et nyt commit (med konkret fix/retrigger), og angiv det nye SHA i PR-tråden.
[scheduler][stagnation-gate] PR #136 er sat i **stuck** på uændret head SHA `e9104cdc449ef2bc7bb7338f5ad73c8c8d56f8fb` gennem >=2 cyklusser med gentagne blocker-kommentarer.
For at undgå retest-loop stoppes nye review/integrator-triggere for denne PR, indtil der foreligger **nyt commit/head SHA**.
Krav for genoptagelse: push et nyt commit (med konkret fix/retrigger), og angiv det nye SHA i PR-tråden.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Why
Issue #130 reports gameplay smoke failure caused by schema mismatch after failed deploy. This change ensures failed deploys do not leave app code ahead of DB schema.
Aligns with release-readiness tracking in #90.
Refs #130
Refs #90
Integrator blocker (severity: blocker)
e9104cdc449ef2bc7bb7338f5ad73c8c8d56f8fbReview completed ✅
Resultat: APPROVED (merge-klar fra review-perspektiv).
try APPROVED
[integrator] PR ikke merge-klar endnu.\n\nSeverity: blocker\nSHA:
e9104cdc449ef2bc7bb7338f5ad73c8c8d56f8fb\nBlokeringer:\n- check CI / test-and-quality (pull_request)=missing\n- check CI / test-and-quality (push)=missing\n\nKonkret fixforslag: adresser punkterne ovenfor, push nyt commit (nyt SHA), og afvent næste integrator-kørsel.[scheduler][stagnation-gate] PR #136 er sat i stuck på uændret head SHA
e9104cdc449ef2bc7bb7338f5ad73c8c8d56f8fbgennem >=2 cyklusser med gentagne blocker-kommentarer.For at undgå retest-loop stoppes nye review/integrator-triggere for denne PR, indtil der foreligger nyt commit/head SHA.
Krav for genoptagelse: push et nyt commit (med konkret fix/retrigger), og angiv det nye SHA i PR-tråden.