finalize changelog

Author: cptpiepmatz

blog/2026-04-11-nushell_v0_112_0.md

@@ -3,18 +3,12 @@ title: Nushell 0.112.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.112.0 of Nu. This release adds...
+excerpt: Today, we're releasing version 0.112.0 of Nu. This release adds structured markdown parsing with `from md`, a new `%` sigil to explicitly call internal commands, and a bunch of new config options to better shape Nu to your workflow, along with improvements to type checking for cell paths.
 ---
 
-<!-- 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.112.0
 
-<!-- TODO: write this excerpt -->
-
-Today, we're releasing version 0.112.0 of Nu. This release adds...
+Today, we're releasing version 0.112.0 of Nu. This release adds structured markdown parsing with `from md`, a new `%` sigil to explicitly call internal commands, and a bunch of new config options to better shape Nu to your workflow, along with improvements to type checking for cell paths.
 
 # Where to get it
 
@@ -34,24 +28,21 @@ As part of this release, we also publish a set of optional [plugins](https://www
 The `from md` is considered a breaking change as previously `open *.md` would return a string.
 :::
 
-We introduced the `from md` command that allows parsing a markdown document and extracting data in a structured manner instead of parsing specific parts of the markdown string and hoping for the best.
+We added a new `from md` command that lets you parse markdown into structured data. Instead of manually pulling pieces out of a markdown string and hoping it works, you now get something much more reliable to work with.
 
 ::: info
-Since `from` commands modify the behavior of `open`, we encourage to discuss whether this is a fitting name or not in a [Github discussion](https://github.com/nushell/nushell/discussions/18011).
-Please state your opinion on this.
+Since `from` commands affect how `open` behaves, we'd love your input on whether the name still makes sense. Join the discussion on [Github](https://github.com/nushell/nushell/discussions/18011) and share your thoughts.
 :::
 
-See the example output [here](#parse-markdown-via-from-md-1).
+Check out the example output [here](#parse-markdown-via-from-md-1).
 
 ## No more shadows, call internals with `%`
 
-Nushell supports the `^` sigil to explicitly state you want to call an external binary.
-This ensures that commands can still be called even if they have a built-in equivalent with the same name or a custom command with the same name.
+Nushell already has the `^` sigil to explicitly call external commands. That way you can still run a binary even if there's a built-in or custom command with the same name.
 
-We had a lot of requests if we could have something similar for internals/builtin commands.
-Thanks to [@fdncred](https://github.com/fdncred) we now have the `%` sigil that does exactly that.
-It uses the initial scope and denies calling externals.
-With it you can ensure you always call an internal and even hidden commands can be called using it.
+A lot of people asked for something similar for internal commands and now we have it. Thanks to [@fdncred](https://github.com/fdncred), the new `%` sigil lets you explicitly call built-ins.
+
+It always uses the initial scope and won't fall back to externals. That means you can reliably call internal commands, even if they're hidden.
 
 ```ansi :no-line-numbers
 > version | get version
@@ -72,11 +63,11 @@ Error: nu::shell::external_command
 0.112.0
 ```
 
-More info in the [main entry](#new-sigil-to-explicitly-call-built-ins).
+More details in the [main entry](#new-sigil-to-explicitly-call-built-ins).
 
 ## Configure Nushell how you like
 
-This release added a lot of new config options.
+This release comes with a bunch of new config options to tweak things to your liking.
 
 ### `$env.config.history.path`
 
@@ -97,9 +88,9 @@ $env.config.history.path = "~/custom/my-history.txt"
 
 </details>
 
-Thanks to [@kx0101](https://github.com/kx0101) we can now configure where the history should be stored.
-This ignores the file format, so make sure your config accommodates for that.
-`null` can also be used to disable history.
+Thanks to [@kx0101](https://github.com/kx0101), you can now choose exactly where your history file lives.
+This ignores the file format, so make sure your config matches.
+You can also set it to `null` to disable history entirely.
 Read [more](#history-file-path-can-now-be-configured).
 
 ### `$env.config.history.ignore_space_prefixed`
@@ -116,7 +107,7 @@ $env.config.history.ignore_space_prefixed = true
 
 </details>
 
-[@guluo2016](https://github.com/guluo2016) added the option to include commands in your history even if prefixed with a space.
+[@guluo2016](https://github.com/guluo2016) added an option to control whether commands starting with a space end up in your history.
 Read [more](#new-option-to-allow-command-with-space-prefixes-to-be-recorded-in-history).
 
 ### `$env.config.auto_cd_implicit`
@@ -134,7 +125,7 @@ $env.config.auto_cd_implicit = false
 
 </details>
 
-[@dxrcy](https://github.com/dxrcy) added the config option to auto-cd into another directory if it exists.
+[@dxrcy](https://github.com/dxrcy) added a config option that lets you automatically `cd` into directories when you type their name.
 Read [more](#new-configuration-option-auto-cd-always).
 
 ### `$env.config.hinter.closure`
@@ -170,7 +161,7 @@ $env.config.hinter.closure = null
 
 </details>
 
-Thanks to [@stuartcarnie](https://github.com/stuartcarnie) Nushell is now able to configure an external hinter via a closure.
+Thanks to [@stuartcarnie](https://github.com/stuartcarnie), you can now plug in your own hinter using a closure.
 Read [more](#added-configurable-external-hinter-closure).
 
 ### `$env.config.table.mode = "frameless"`
@@ -190,8 +181,8 @@ $env.config.table.mode = "rounded"
 
 </details>
 
-[@Benjas333](https://github.com/Benjas333) added the new table style "frameless".
-See an example [here](#new-table-style-frameless).
+[@Benjas333](https://github.com/Benjas333) added a new table style called "frameless".
+Take a look [here](#new-table-style-frameless).
 
 ### `$env.config.color_config.binary_*`
 
@@ -221,15 +212,17 @@ $env.config.color_config.binary_non_ascii = "yellow_bold"
 
 </details>
 
-[@ian-h-chamberlain](https://github.com/ian-h-chamberlain) added more color config options for the binary values in our hex viewer in [#17887](https://github.com/nushell/nushell/pull/17887).
+[@ian-h-chamberlain](https://github.com/ian-h-chamberlain) added more color options for binary data in the hex viewer in [#17887](https://github.com/nushell/nushell/pull/17887).
 
 ## Types via cell.paths! - `cell-path-types`
 
 <ExperimentalOption option="cell-path-types" />
 
-[@blindFS](https://github.com/blindFS) added a new experimental option to make type inference smarter when using cell paths.
-Previously we only got errors for wrongly used nested types at runtime. Now we can even detect them at parse time.
-For some examples see [this](#new-experimental-option-cell-path-types).
+[@blindFS](https://github.com/blindFS) introduced a new experimental option that makes type inference smarter when working with cell paths.
+
+Before this, issues with nested types would only show up at runtime. Now they can already be caught during parsing.
+
+Check out some examples [here](#new-experimental-option-cell-path-types).
 
 # Changes <JumpToc/>
 
@@ -1151,9 +1144,9 @@ Two changes:
 - Added `Type::table()` to `bytes collect` input types so pipelines like `0..128 | each {} | into binary --compact | bytes collect` work without requiring an explicit `collect` first
 - Deduplicated types in `combined_type_string` so error messages say "binary, table, or record" instead of "binary, binary, binary, binary, table, or record"
 
-### Builtin commands now support `null` for optional parameters <JumpToc/> <PrBy :pr="17753" user="0xRozier" />
+### built-in commands now support `null` for optional parameters <JumpToc/> <PrBy :pr="17753" user="0xRozier" />
 
-Optional positional parameters in builtin commands now accept `null`, treating it as if the argument was omitted. This allows custom commands to wrap builtins and transparently forward optional parameters:
+Optional positional parameters in built-in commands now accept `null`, treating it as if the argument was omitted. This allows custom commands to wrap built-ins and transparently forward optional parameters:
 
 ```ansi :no-line-numbers
 > def wraps-first [rows?: int] { [1, 2, 3] | first $rows }
@@ -1398,7 +1391,7 @@ Thanks to all the contributors below for helping us solve issues, improve docume
 
 | author                                                       | title                                                                                                                          | link                                                    |
 | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------- |
-| [@0xRozier](https://github.com/0xRozier)                     | fix: allow passing null to optional positional params in builtin commands                                                      | [#17753](https://github.com/nushell/nushell/pull/17753) |
+| [@0xRozier](https://github.com/0xRozier)                     | fix: allow passing null to optional positional params in built-in commands                                                     | [#17753](https://github.com/nushell/nushell/pull/17753) |
 | [@Bahex](https://github.com/Bahex)                           | feat(std-rfc/xml xaccess): experimental rewrite of `std/xml xaccess`                                                           | [#16804](https://github.com/nushell/nushell/pull/16804) |
 | [@Bahex](https://github.com/Bahex)                           | feat: make `Span`'s `Debug` impl succinct                                                                                      | [#17782](https://github.com/nushell/nushell/pull/17782) |
 | [@Bahex](https://github.com/Bahex)                           | feat: `test_record!` macro for convenience                                                                                     | [#17797](https://github.com/nushell/nushell/pull/17797) |