Skip to content

Commit 6ae3428

Browse files
committed
Add note about regression and move std/clip mention to additions
1 parent 575fc67 commit 6ae3428

File tree

1 file changed

+27
-7
lines changed

1 file changed

+27
-7
lines changed

blog/2025-07-23-nushell_0_106_0.md

Lines changed: 27 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -27,12 +27,13 @@ As part of this release, we also publish a set of optional [plugins](https://www
2727
- [_Improvements to errors and warnings_](#improvements-to-errors-and-warnings-toc)
2828
- [_Changes_](#changes-toc)
2929
- [_Breaking changes_](#breaking-changes-toc)
30+
- [_Regression: bare word interpolation on both sides does not work_](#regression-bare-word-interpolation-on-both-sides-does-not-work-toc)
3031
- [_`path` and `directory` command arguments are no longer expanded_](#path-and-directory-command-arguments-are-no-longer-expanded-toc)
3132
- [_Stricter compound assignment operator type checking_](#stricter-compound-assignment-operator-type-checking-toc)
3233
- [_`parse`: unmatched optional capture groups are now `null`_](#parse-unmatched-optional-capture-groups-are-now-null-toc)
33-
- [_`clip` graduates from `std-rfc`_](#clip-graduates-from-std-rfc-toc)
3434
- [_Additions_](#additions-toc)
3535
- [_Experimental options_](#experimental-options-toc)
36+
- [_`clip` graduates from `std-rfc`_](#clip-graduates-from-std-rfc-toc)
3637
- [_Improved documentation, errors, and warnings_](#improved-documentation-errors-and-warnings-toc)
3738
- [_Commands_](#commands-toc)
3839
- [_Deprecations_](#deprecations-toc)
@@ -80,6 +81,25 @@ This release adds some polish to errors and warnings. It also comes along with s
8081

8182
## Breaking changes [[toc](#table-of-contents)]
8283

84+
### Regression: bare word interpolation on both sides does not work [[toc](#table-of-contents)]
85+
86+
Unfortunately, we caught a regression shortly after release. Bare word interpolations (introduced in 0.105.0) which have expressions before and after a string component cause an error in 0.106.0. This was caused by the fix introduced in [#16204]. Here's an example which worked in 0.105.0, but not 0.106.0:
87+
88+
```nushell
89+
let x = 123
90+
($x)/foo/($x)
91+
```
92+
93+
Note that these forms do still work in 0.106.0:
94+
95+
```nushell
96+
let x = 123
97+
($x)/foo
98+
foo/($x)
99+
```
100+
101+
We plan to address this with a 0.106.1 patch release in the coming days. We are hoping to resolve the regression, while still keeping the bug fix from [#16204].
102+
83103
### `path` and `directory` command arguments are no longer expanded [[toc](#table-of-contents)]
84104

85105
As of [#15878], unquote file/directory paths as command arguments will no longer be expanded into absolute paths. This may break scripts which rely on the old absolute expansion. These paths should now be manually expanded.
@@ -140,12 +160,6 @@ Now it's clear:
140160
[[user, action]; ["0", bar], ["0", ""], ["0", null]]
141161
```
142162

143-
### `clip` graduates from `std-rfc` [[toc](#table-of-contents)]
144-
145-
After spending some time in `std-rfc`, with [#15877] `clip` module graduates to `std`, the first module from `std-rfc` to do so!
146-
147-
Using `std-rfc/clip` will give a deprecation warning, instructing you to switch to the `std` version.
148-
149163
## Additions [[toc](#table-of-contents)]
150164

151165
### Experimental options [[toc](#table-of-contents)]
@@ -250,6 +264,12 @@ $val.foo.0
250264
# => A
251265
```
252266

267+
### `clip` graduates from `std-rfc` [[toc](#table-of-contents)]
268+
269+
After spending some time in `std-rfc`, with [#15877] `clip` module graduates to `std`, the first module from `std-rfc` to do so!
270+
271+
Using `std-rfc/clip` will give a deprecation warning, instructing you to switch to the `std` version.
272+
253273
### Improved documentation, errors, and warnings [[toc](#table-of-contents)]
254274

255275
- With [#15892], text written in backticks inside help text will now be highlighted as code. If it's valid Nushell code, it will be highlighted as such. Otherwise, it will use a "dimmed" style. You can make use of this yourself in custom command documentation as well! Here's what this looks like with some examples on the `select` command documentation (notice `name` and `first 4` being highlighted):

0 commit comments

Comments
 (0)