You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blog/2025-07-30-nushell_0_106_1.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,6 @@ As part of this release, we also publish a set of optional [plugins](https://www
25
25
-[_Fix for builds on NetBSD and FreeBSD_](#fix-for-builds-on-netbsd-and-freebsd-toc)
26
26
-[_Fixed warnings for plugin builds_](#fixed-warnings-for-plugin-builds-toc)
27
27
-[_Full changelog_](#full-changelog-toc)
28
-
<!-- TODO: once all the content below is finished and committed, `use nu_scripts/make_release/release-note/notes.nu *` and run `write-toc $this_file`. -->
29
28
30
29
# Changes [[toc](#table-of-contents)]
31
30
@@ -34,7 +33,7 @@ As part of this release, we also publish a set of optional [plugins](https://www
34
33
### Fixed regression in the bare string interpolation [#16235][[toc](#table-of-contents)]
35
34
36
35
While fixing another parser bug in 0.106.0 we accidentally introduced a [regression which restricted certain forms of direct string interpolation using parenthesized expressions with bare words](https://www.nushell.sh/blog/2025-07-23-nushell_0_106_0.html#regression-bare-word-interpolation-on-both-sides-does-not-work-toc).
37
-
Thanks to a fix by @[Bahex] the following form of string interpolation again works without issue:
36
+
Thanks to a fix by [@Bahex] the following form of string interpolation again works without issue:
38
37
39
38
```nushell
40
39
let x = 123
@@ -48,11 +47,11 @@ The recent change to [`get` to rename `--ignore-errors` to `--optional`](https:/
48
47
49
48
### Fix for builds on NetBSD and FreeBSD [[toc](#table-of-contents)]
50
49
51
-
BSD builds failed due to more restrictive Rust compiler warnings triggered in our BSD platform code. This has been fixed in [#16266] and [#16275] by @[0323pin] and @[sholderbach]
50
+
BSD builds failed due to more restrictive Rust compiler warnings triggered in our BSD platform code. This has been fixed in [#16266] and [#16275] by [@0323pin] and [@sholderbach]
52
51
53
52
### Fixed warnings for plugin builds [[toc](#table-of-contents)]
54
53
55
-
When building plugins with our Rust `nu-plugin-core 0.106.0` crate you may have encountered compiler warnings. This has been addressed by @[cptpiepmatz] in [#16279]
54
+
When building plugins with our Rust `nu-plugin-core 0.106.0` crate you may have encountered compiler warnings. This has been addressed by [@cptpiepmatz] in [#16279]
56
55
57
56
# Full changelog [[toc](#table-of-contents)]
58
57
@@ -64,10 +63,10 @@ When building plugins with our Rust `nu-plugin-core 0.106.0` crate you may have
64
63
|[sholderbach]| Port `unsafe_op_in_unsafe_fn` fix to FreeBSD |[#16275]|
65
64
|[cptpiepmatz]| Don't import `IoError` on `nu-plugin-core` without `local-socket`|[#16279]|
0 commit comments