Repository navigation
fix(ci): retain production project context for MailOut preparation - #287
Merged
Merged
Conversation
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
November 20, 2026 19:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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=falseafter 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.