Skip to main content

Release v0.0.76

· 8 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release adds AI to the task palette and sharpens the caching and concurrency primitives. A new Dapr Conversation task (TaskType = 20) invokes an LLM/AI provider (OpenAI, Anthropic, Bedrock, …) provider-agnostically through the Dapr Conversation building block (#844). Function result caching gains vary-by headers — varyByHeaders / varyByHeaderPrefixes feed a varyKey(context) key-expression helper so one function keeps separate cache variants per header value (#839). Flow-level cache tuning is consolidated under a single attributes.config object (config.functionCache.ttlSeconds), the author-controlled TTL for the built-in instance functions (#846). Distributed resource locks become production-ready with idempotent release and automatic terminal cleanup (#840), plus a per-subInstance lock key for subflow terminal-outcome propagation (#845). Wizard states are now treated like normal states in the State/View functions (#838). The release also fixes author Content-Type preservation (#847), case-insensitive request-header normalization (#841), and init mappings support for publish (#848). This release runs on component schema 0.0.51.

Release v0.0.71

· 11 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release makes vNext event-driven and query-friendly. Event-driven workflows let an external pub/sub message start a new instance (workflow-level event) or advance an existing one through a triggerType: 3 transition, correlated by an IEventMapping script (#86). A fluent instance query language (InstanceQuery) replaces hand-written GraphQL filter JSON in script mappings — one builder powers event selectors, GetInstancesTask filter specs, and raw list-endpoint query strings. A new GetInstance task (TaskType = 19) returns a full single-instance projection (#806), and function result caching serves a repeat function call from a Dapr state store with a single cache read. Instance start/transition and function endpoints now accept application/x-www-form-urlencoded bodies (#825); output scripts can set the content-type response header and async operations return 202 Accepted (#819). The State function response gains a master schema HREF backed by a new master schema function (#821) and an always-present interaction directive object for long-poll clients. The component schema also ships a new data-vocab vocabulary (x-context-source / x-context-target) for schema-driven client context binding. This release runs on component schema 0.0.50.

Release v0.0.68

· 10 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release introduces four new capabilities and a substantial subflow stability hardening set. Workflow output mapping lets a flow declare an output script whose result is returned directly as the HTTP response body — with the script's status code and headers — on synchronous start/transition calls (#785, #790). Free-form payload support allows instance start and transition endpoints to accept arbitrary JSON bodies without the standard attributes envelope, resolved automatically or via the x-vnext-payload-mode header (#785, #788). A new built-in StateStore task (TaskType = 17) brings a caching primitive to the workflow pipeline on top of Dapr state stores, with get / set / delete commands, TTL, and optimistic concurrency (#792). Transition history now snapshots the externally visible state per transition: effectiveState, effectiveStateType, effectiveStateSubType, and stage (#793). Five fixes eliminate an entire class of stuck-subflow scenarios in deep and synchronous subflow chains (#784, #787, #789, #791, #794). This release runs on component schema 0.0.49.

Release v0.0.66

· 5 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release brings one significant new capability and three targeted fixes. State-level notifications land as a first-class workflow primitive: a state can now declare a notifications array that the runtime enqueues durably after the transition pipeline completes, decoupling notification dispatch from the task pipeline entirely and guaranteeing state data is fully persisted before delivery (#722). Root instance ID propagation threads a stable ancestor identifier through deep subflow chains so that a single search key in Jaeger or structured logs surfaces every span and log line across the full execution graph (#769). Two fixes round out the release: UTF-16 allocation on every buffered request body is eliminated by switching the raw-body contract from string to ReadOnlyMemory<byte> (#773), and a race condition causing EF Core concurrency exceptions when fetching multiple extensions in parallel is resolved by giving each concurrent fetch its own DbContext scope (#771). This bump advances the component schema to 0.0.48.

Release v0.0.62

· 8 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release sharpens four integration-facing capabilities and lands a runtime-discovery tool. HTTP Task gains a configurable contentType so requests can carry payloads other than JSON, with byte-exact body preservation for signing scenarios (#742). States can declare a long-poll interaction, making it declarative when a client workflow manager should terminate a long poll — so different clients can model their own stop points across a process (#717). Multi-task functions now forward output ScriptResponse headers and status code, giving output handlers control over the final function response shape (#748). The new vnext-runtime MCP server exposes component, runtime, and metadata discovery to MCP-capable agents, so AI tooling can be wired directly against a domain's runtime (#333). The async transition pipeline adds a direct Dapr-enqueue continuation mode with outbox fallback (#744), and the authorization model now treats deny-only role grant sets as blacklists (default allow) (#736). Three fixes round out the release: SOAP task compilation and escaping (#738), chain-token gating for child sub-processes (#730), and domain replacement of subprocess references (#729). This bump advances the component schema to 0.0.47.

Release v0.0.60

· 8 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release lands two long-tracked capabilities and hardens the transition pipeline. Sandboxed, component-referenced custom C# script helpers let consuming teams ship their own helper classes as .csx components and reference them from a mapping's scripts.helpers, compiled and run under a two-layer sandbox (#710). State aliases expose role-scoped, multi-language state labels without touching the internal state identity (#648). The transition pipeline gains configurable async execution modes — continuation enqueueing, transition atomicity, chain-ownership gating, and a chain reaper for stuck instances (#725). FunctionScope is now enforced consistently on every function-invocation entry point (#709). A correctness fix removes EF compiled queries (broken under PGBouncer + multi-schema) and makes the duplicate-key check deterministic (#715), and an operations hardening pass disables production Swagger and promotes function/mapping failures to Error-level logging (#724). This bump also advances the component schema to 0.0.46.

Release v0.0.58

· 6 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release closes the gap in subflow fault handling: a faulted child now propagates through the parent's error boundary chain instead of leaving the parent stuck in Busy (#699). Function responses and wizard-state behavior are extended — acceptedStatusCodes are honored end-to-end so rawResponse=true endpoints can forward structured HTTP 400s, and wizard states resolve transition views first while reporting hasView in a loop-safe way (#697). A hotfix standardizes instance audit columns via a shared base model and fixes the async reserved-transition lock (#644). The runtime repository's own documentation was rebuilt into an architecture-first structure (#693), and vocabulary-aware runtime schema validation was added (PR #692). This bump also advances the component schema to 0.0.43.

Release v0.0.57

· 4 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release hardens two correctness paths and improves human-task query performance. JSON canonicalization is now safe against duplicate object keys regardless of casing or the active DictionaryKeyPolicy (#688). The ErrorBoundary pipeline profile changes behavior: it now allows auto-chaining, so recovery transitions can continue into automatic follow-ups after a boundary fires — a deliberate behavior change. Human-task instance listing is parallelized with bounded concurrency, and predefined PreviousUser / PreviousBehalfOfUser role checks are optimized (#689). The release also exposes ScriptBase XML helpers and the function-level rawResponse flag.

Release v0.0.56

· 3 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release promotes SoapTask to a first-class task type (Type 16) for calling SOAP 1.1 / 1.2 web services directly from a workflow, closing the #647 investigation into whether SOAP integration could be handled by the existing HttpTask. The conclusion: a dedicated abstraction is warranted because SOAP envelopes need raw-XML body handling, a SOAPAction header, and the ability to treat HTTP 500 SOAP Faults as inspectable business responses.

Release v0.0.55

· 5 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release introduces SoapTask as a first-class task type for SOAP 1.1/1.2 web service integrations, expands Functions to support POST, PATCH, and DELETE verbs alongside GET, and adds a layered timeout model for workflow job execution that eliminates indefinitely stuck Busy instances. ScriptBase gains XML helper methods (ParseXml, XmlToString) to support SOAP response handling in mapping scripts. A new Deployment documentation section covers Helm chart installation and the Release Viewer tool. Transition Annotations receive documented platform-convention keys, and the View Concept guide is extended with the State View / Transition View interaction model. A schema correction moves NotificationTask configuration under attributes.