v0.8.0
Axial 0.8.0
Breaking changes
Process.run is now the command-line host runner: it starts a Flow with live process services and returns a host
exit code. The equivalent DSL form is workflow |> run.
Process.runWith environment workflow starts a process Flow with an application's existing environment. The
environment supplies IConsole for typed failure reporting and may contain any other application services.
The former lazy Process.run is renamed to Process.toFlow. It converts a ProcessSpec into a Flow that runs only
when its enclosing Flow runs. Axial.Process.Script is removed; use Process.run, Process.runWith, or their DSL
forms instead.
Process.console is added as the full API equivalent of DSL console. It creates a lazy Flow that forwards both
output channels to the host console. captureParallel now explicitly applies complete capture to every command.
Process.command now accepts an interpolated command template, such as Process.command $"git status", with each
hole preserved as one native argument. The previous executable-and-list form is renamed to Process.commandArgs.
Documentation and release workflow
The documentation site now separates Axial Core, Axial.Process, and Axial.HttpClient into focused documentation
sets, with a package catalogue linking each set. The homepage logo scales to the available viewport on small screens
and is larger on wider displays.
The Getting Started and Why Flow guides now introduce Flow<'env, 'error, 'value> as capabilities, expected failure,
and successful value. They explain why Axial manages effects through one composable runtime model, rather than treating
the type signature as a substitute for cancellation and resource ownership. The Flow type diagram has light and dark
variants.
The Axial.Process landing page now starts with a compact script and links to focused guides for command composition,
output capture, streaming, failures, scripts, worked examples, and application Flow integration. The guides link DSL
names to their API reference entries and distinguish command construction, lazy conversion to Flow, and host execution.
The Task-versus-Flow comparison now links each scenario to its complete GitHub source and the tests that verify the
claimed behavior.
Release documentation is now recorded as an immutable, committed history. The site renders that history on every
deployment, so its version switcher reflects the published Axial releases. The release workflow verifies a candidate
capsule against that history before publication, records the published capsule after publication, and waits for the
Pages deployment before publishing NuGet packages.
FsLiveDocs is updated to 0.6.1, which fixes Markdown and cross-references immediately following rendered F# code
fences.