added prose highlights and excerpt

Author: cptpiepmatz

blog/2026-07-04-nushell_v0_114_0.md

@@ -3,18 +3,12 @@ title: Nushell 0.114.0
 author: The Nu Authors
 author_site: https://www.nushell.sh/blog
 author_image: https://www.nushell.sh/blog/images/nu_logo.png
-excerpt: Today, we're releasing version 0.114.0 of Nu. This release adds...
+excerpt: Today, we're releasing version 0.114.0 of Nu. This release brings sharper type checking, POSIX-style `--` option parsing, the new `run` command for pipeline-friendly scripts, and nice built-in support for working with Semantic Versioning.
 ---
 
-<!-- TODO: complete the excerpt above -->
-
-<!-- NOTE: start from the TODO all the way at the bottom (and sort of work your way up) -->
-
 # Nushell 0.114.0
 
-<!-- TODO: write this excerpt -->
-
-Today, we're releasing version 0.114.0 of Nu. This release adds...
+Today, we're releasing version 0.114.0 of Nu. This release brings sharper type checking, POSIX-style `--` option parsing, the new `run` command for pipeline-friendly scripts, and nice built-in support for working with Semantic Versioning.
 
 # Where to get it
 
@@ -28,41 +22,52 @@ As part of this release, we also publish a set of optional [plugins](https://www
 
 # Highlights and themes of this release <JumpToc/>
 
-- type system improvements
+## The type checker got new glasses <JumpToc/>
+
+[@Bahex](https://github.com/Bahex) continued tightening up Nushell's type system this release. Commands can now infer output types from pipeline input more precisely, `$in` gets typed from the surrounding pipeline, optional values carry their `nothing`-ness more honestly, and `let` bindings in pipelines no longer have to shrug and call everything `any`.
+
+This means some mistakes move from "surprise, runtime error" to "hey, maybe fix that before running it". Very rude of the parser, but also very helpful.
+
+There is also one important default change: `enforce-runtime-annotations` is now opt-out, so runtime assignment annotations get checked by default.
+
+Read the details in the first [type system entry](#type-system-improvements-1), the second [type system entry](#type-system-improvements), and the note about [`enforce-runtime-annotations`](#promoted-enforce-runtime-annotations-to-opt-out).
+
+## `--` means "no really, stop parsing flags" <JumpToc/>
+
+Thanks to [@fdncred](https://github.com/fdncred), Nushell commands now understand the classic POSIX `--` end-of-options delimiter. If you need to pass `-weird`, `--looks-like-a-flag`, or similar gremlins as plain positional values, you can now do that without trying to outsmart the parser.
+
+```nushell
+def greet [--upper, name] { if $upper { $name | str uppercase } else { $name } }
+greet -- -Alice
+```
+
+That `-Alice` is now just Alice having a dash day, not an accidental flag.
+
+Take a look at the main [`--` option parsing entry](#added-posix-style-option-parsing-for-nushell-commands) and the follow-up [`--wrapped` fix](#fixed-a-bug-in-option-parsing).
+
+## Scripts can join the pipeline with `run` <JumpToc/>
 
-  - by Bahex
-  - #type-system-improvements-1
-  - #type-system-improvements
-  - #promoted-enforce-runtime-annotations-to-opt-out
+The new `run` command from [@fdncred](https://github.com/fdncred) lets a Nushell script behave like a pipeline stage. Pipe data in, let the script transform it, and pipe the result onward. Tiny reusable pipeline workers, basically.
 
-- `--` support
+```nushell
+"Hello Nushell!" | run shout.nu | str camel-case
+```
+
+Scripts can be simple bare pipeline transforms or define a `main` entry point, and they run in isolation so their local bits do not leak back into your session.
 
-  - by fdncred
-  - #added-posix-style-option-parsing-for-nushell-commands
-  - #fixed-a-bug-in-option-parsing
+See more examples [here](#added-run-command-for-using-scripts-in-pipelines).
 
-- `run` command
+## SemVer is a real value now <JumpToc/>
 
-  - by fdncred
-  - #added-run-command-for-using-scripts-in-pipelines
+Nushell now has semantic version support, also from [@fdncred](https://github.com/fdncred). You can parse SemVer strings, turn them into records, build them back up, sort them correctly, and bump versions without doing string surgery with safety scissors.
 
-- semver commands
-  - by fdncred
-  - #added-semantic-version-parsing-and-commands
+```nushell
+'1.2.3-alpha.1' | into semver | semver bump release
+```
 
-<!-- NOTE: if you wanna write a section about a breaking change, when it's a very important one,
-    please add the following snippet to have a "warning" banner :)
-    > see [an example](https://www.nushell.sh/blog/2023-09-19-nushell_0_85_0.html#pythonesque-operators-removal)
+If your scripts deal with releases, package versions, or "is `1.10.0` bigger than `1.2.0`?" moments, this should make life nicer.
 
-    ```md
-    ::: warning Breaking change
-    See a full overview of the [breaking changes](#breaking-changes)
-    :::
-    ```
--->
-<!-- NOTE: see https://vuepress.github.io/reference/default-theme/markdown.html#custom-containers
-    for the list of available *containers*
--->
+Read the full SemVer tour [here](#added-semantic-version-parsing-and-commands).
 
 # Changes <JumpToc/>