Skip to content

fix(ci): retain production project context for MailOut preparation - #287

Merged
lweberru merged 2 commits into
mainfrom
fix/prod-mailout-project-scope
Nov 20, 2026
Merged

lweberru merged 2 commits into
mainfrom
fix/prod-mailout-project-scope

Conversation

@lweberru

Copy link
Copy Markdown
Collaborator

The v2.2.3 production deployment stopped before Cloud Foundry staging with mailout_bindings_invalid. The protected project variable was supplied only to backend preparation; application preparation received the SMTP binding without its target project and correctly rejected it.

Pass the protected production project ID at deployment-job scope so both preparation phases use the same reviewed project. Retain sender, project and credential validation. A regression checks the actual workflow variable scope; the production runtime fixture verifies accepted SMTP settings and rejection of absent or mismatched projects. English/German operator diagnostics are updated.

Validation: the regression failed before the change; all 34 targeted production, release preparation/lifecycle and MailOut binding checks pass afterward. No application or Runner package changes. Redeploy the existing, successfully Dev-tested v2.2.3 release with publish=false after merging; preserve the immutable published artifacts and normal production approval.

Follow-up to #283 and failed production run 44797809773. The previous production application was not replaced.

@lweberru
lweberru merged commit dc7a087 into main Nov 20, 2026
16 checks passed
@lweberru
lweberru deleted the fix/prod-mailout-project-scope branch November 20, 2026 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant