New POST /v1/workflows-definition/journey-context:usages endpoint was added for reading where a journey context is used
Automation tasks in a flow template can now ask for a note when they are executed, restrict which closing reasons may be picked, and have the email they send reviewed before it goes out, through new optional tasks[].automation_config.allow_execution_note, automation_config.eligible_closing_reason_ids, and automation_config.email_review fields — accepted on POST /v2/flows/templates and PUT /v2/flows/templates/{flowId} and returned wherever flow templates are read
POST /v1/workflows/definitions can now respond with 409 when the definition conflicts with an existing one