This release consolidates seven interim versions (v0.0.44 through v0.0.49) into the stable v0.0.50 release. The primary themes are pipeline correctness, infrastructure resilience, performance optimization, and observability.
This release improves reliability and consistency across flows, tasks, and domain events: cancel transitions on single-flow definitions validate correctly, TriggerTask family tasks map HTTP status codes on local execution for errorBoundary matching, and AmbientServiceProvider scopes restore domain event delivery (including effective-state and subflow completion paths). GetInstance / GetInstanceData honor the version query parameter, GroupBy and aggregation work when filters reference Instance table columns, DaprServiceTask runs without invalid trace context for non-flow functions, and definition cache warm-up no longer loads the full active-instance set into memory (OutOfMemoryException fix). New capabilities include auto-transition rules evaluated with Dynamic Expresso over instance JSONB, and instance-data–based authorization using $user, $role, and $userBehalfOf JSONPath-style selectors plus $InstanceBehalfOfStarter and $PreviousBehalfOfUser.
This release shifts flow database schema creation and migration to deploy time via a DB-Migrator job instead of running migration checks on every start and transition request. It improves observability with consistent structured logging and TaskCoordinator span tracing (Aether). For synchronous start and transition calls (sync=true), responses now include mapped instance data (attributes, ETags, extensions) in addition to id and status. User-defined functions support multi-task execution with ordered onExecutionTasks and optional output mapping via IOutputHandler. SubFlow definitions can use an overrides object to replace transition roles, state query roles, timeouts, and related behavior while keeping legacy view override compatibility. ScriptBase adds collection and dynamic-object helpers (CreateObject, GetList, ListFilter, ListSelect, and related APIs) for safer in-script shaping of Instance.Data. AutoMapper has been replaced by Mapperly in the Aether SDK, and AutoMapper is no longer a vNext dependency.