Nushell 0.114 Keeps Structured Shell Pipelines Moving Toward 1.0

Nushell published version 0.114.0 on July 4, 2026, continuing its pre-1.0 release line rather than declaring the compatibility milestone prematurely. The numbering matters: Nushell’s project still presents 1.0 as a destination, not an already completed release.

The pipeline carries values, not only lines

Traditional shells connect byte streams. Nushell commands instead commonly exchange typed values organized into records, lists, and tables. A listing can therefore remain structured while later stages select columns, filter rows, sort numeric fields, and render the final result.

ls | where size > 10mb | sort-by size | select name size modified

This does not abolish text: external programs still consume and produce bytes, and Nushell includes parsers and serializers to cross that boundary. The distinction is that built-in pipeline stages can retain types rather than forcing every intermediate step through ad hoc text parsing.

Why a long pre-1.0 period can be responsible

Shell syntax, command names, plugin interfaces, and serialized data formats become expensive to change after users build dotfiles and automation around them. A pre-1.0 label allows the project to continue correcting those interfaces while communicating that compatibility can still move between releases.

That also makes release notes essential operational reading. Users should test scripts against a pinned Nushell version, review breaking changes before upgrades, and avoid treating examples for one 0.x release as a permanent language contract.

What this release represents

Version 0.114 is another incremental delivery in a project that describes itself as “a new type of shell.” Its durable contribution is the experiment itself: applying data-frame-like interaction and a purpose-built language to jobs that conventional shells approach as text transformations.

Whether Nushell replaces a POSIX shell for a given user is a separate decision. It can be an effective interactive data tool while Bash, Dash, or another POSIX-oriented shell remains the portability target for system scripts.

Where the project’s structured-data premise actually came from

Nushell traces to a collaboration between Jonathan Turner, formerly of Microsoft and the Rust compiler team, and Yehuda Katz — the idea crystallized when Katz was demonstrating PowerShell’s object-pipeline capabilities and Turner recognized a broader, largely unexplored design space in how shells could pass structured data between commands rather than forcing everything through plain text. The project was first publicly announced on August 23, 2019, and the core inspiration — structured values flowing through a pipeline instead of byte streams requiring ad hoc parsing at every stage — has remained the project’s defining premise across the many 0.x releases since, including 0.114.

Why the destination matters more than the version number itself

The project’s own “Road to 1.0” post, published years before 0.114 shipped, framed 1.0 explicitly as a compatibility commitment rather than a marketing milestone — reaching it means the team is confident enough in the current syntax, command names, and data formats that future changes will follow a genuine stability and deprecation policy, rather than the freer, more experimental churn a pre-1.0 project can still afford. Every 0.x release along the way, 0.114 included, represents incremental progress toward that specific bar rather than being a lesser or incomplete version of some already-decided final design — the team has been explicit that reaching 1.0 prematurely, before the interfaces genuinely felt settled, would have cost considerably more in forced future breakage than continuing to iterate openly, in the open, as a pre-1.0 project instead.

Related:

Sources: