v1.2.3
Resterm now rejects invalid workflow definitions before execution, preventing directive typos or invalid failure settings from silently changing how a workflow runs.
Fixed
Catch workflow directive typos before running
An unknown directive inside a workflow definition is now a parse error:
# @workflow deploy
# @step Create using=Create
# @stpe Verify using=VerifyPreviously, @stpe was ignored and the workflow could run without the intended Verify step. Resterm now reports the mistake and refuses to run the file until it is fixed. The parser continues reading the remaining workflow so it can report additional problems in one pass.
Unknown directives at file or request scope remain non-fatal warnings, preserving the behavior introduced in v1.2.2.
Stricter workflow validation
@workflownow requires a name.- Empty or unsupported
on-failurevalues on@workflowand@stepare rejected instead of silently falling back to the default behavior. - Valid workflows retain the same parsing and execution behavior as before.
- Request directives remain request scoped, including when their requests are executed from a workflow.