VOR Stream v26.2.0 introduces a redesigned interface, interactive scenario building, and a preview of VOR Digital Teams for assisted work with models and playpen files. Process navigation helps analysts follow a calculation through its inputs and outputs, while a new change-log export presents definition changes in a workbook built for audit review.
VOR Stream v26.1.5 is the fifth patch release on the v26.1 line and a security release. It updates the messaging client that carries data between the nodes of a process, the library that validates API tokens, the runtime the message broker runs on, and components across the web application and the user guide. Processes, models, studies and screens work as they do on v26.1.4, and the upgrade applies no database migrations.
VOR Stream v26.1.4 is the fourth patch release on the v26.1 line, and it concentrates on correctness and scale. A process that reads a file, table or S3 object into a queue delivers every row it read to the consuming node. The Waterways outputs download serves the run you selected. Four screens load in a fixed amount of database work regardless of how much data sits behind them, so a playpen that has accumulated years of studies and uploads opens as readily as a new one. The formula language gains a reference page, a beginner tutorial and four worked use cases, and the two aggregate functions that treated missing values differently from the rest now follow the same convention. A broad set of security updates spans the engine runtime, the web application, the Python dependency tree and the components the installer bundles.
VOR Stream v26.1.3 is the third patch release on the v26.1 line and the most
capability-rich of the three. It adds two statistical functions to
structured-model transformations, brings the Model Performance and Run Models
panels to structured models, and ships a suite of task-specific agent skills
served straight from the vor binary. It also strengthens how runs behave when
a node hits an error, keeps subprocess execution conditions in step with the
rest of a process, and lets large dictionary imports finish at scale. The user
and admin guides are joined into one cross-linked site, and a broad set of
security updates spans the engine runtime, the web application, and the
components shipped by the installer.
VOR Stream v26.1.2 is the second patch release on the v26.1 line and is primarily a security and operational reliability release. A broad sweep of CVE patches has been applied across the Go runtime, Django, and dozens of transitive Python and Node dependencies. Seven bugs reported from the field have been fixed in the engine, Django, and CLI, including two engine issues that affected correctness or reliability under load. A single new deployment capability rounds out the release: a custom Caddy imports directory that survives Ansible redeploys. There are no breaking changes; v26.1.2 is a drop-in upgrade from v26.1.1.
VOR Stream v26.1.1 is the first patch release on the v26.1 line and focuses on what comes after a big launch: closing the loop on the edge cases that surface as customers exercise new features in production. Upgrades from v25.x are dramatically faster against large datasets, the new Risk Factor and Structured Model workflows shipped in v26.1.0 have been hardened against several reported edge cases, administrators can now manage custom upload type permissions through a self-service UI, and a broad sweep of customer-reported security findings against the v26.1.0 package has been addressed. There are no breaking changes; v26.1.1 is a drop-in upgrade.
VOR Stream v26.1.0 makes model definition faster and more accessible. The headline feature is Structured Model Definitions -- a visual editor that lets you build regression models directly in the UI without writing a single line of code. Combined with a complete Risk Factor Management system and a new automated Model Node, this release reduces the effort required to go from model concept to production execution. Under the hood, critical stability improvements eliminate several engine crashes and data integrity issues that affected concurrent workloads.