fix(workflows): execute email steps from template relation - #19
Merged
Merged
Conversation
This was referenced Aug 28, 2026
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.
Outcome
Valid API-created
SEND_EMAILsteps now execute from their relational template binding. Recipient-only config no longer fails runtime validation, and a stale duplicated JSONtemplateIdcannot override the relation.Closes #18.
Paired upstream PR: useplunk#472
Proof
Production follow-through
After merge, deploy one immutable image digest to API, worker, and dashboard; read back all three pins; then rerun the synthetic opt-in against the unchanged live workflow.