diff --git a/blog/2025-06-10-nushell_0_105_1.md b/blog/2025-06-10-nushell_0_105_1.md
new file mode 100644
index 00000000000..73f77565592
--- /dev/null
+++ b/blog/2025-06-10-nushell_0_105_1.md
@@ -0,0 +1,70 @@
+---
+title: Nushell 0.105.1
+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.105.1 of Nu. This release adds a fix to make `cargo install nu` possible again.
+---
+
+# Nushell 0.105.1
+
+Today, we're releasing version 0.105.1 of Nu. This release adds a fix to make `cargo install nu` possible again.
+
+# Where to get it
+
+Nu 0.105.1 is available as [pre-built binaries](https://github.com/nushell/nushell/releases/tag/0.105.1) or from [crates.io](https://crates.io/crates/nu). If you have Rust installed you can install it using `cargo install nu`.
+
+As part of this release, we also publish a set of optional [plugins](https://www.nushell.sh/book/plugins.html) you can install and use with Nushell.
+
+# Table of contents
+
+- [_Highlights and themes of this release_](#highlights-and-themes-of-this-release-toc)
+  - [_Reverted `coreutils` to fix `cargo install`_](#reverted-coreutils-to-fix-cargo-install-toc)
+- [_Full changelog_](#full-changelog-toc)
+
+# Highlights and themes of this release [[toc](#table-of-contents)]
+
+<!-- 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)
+
+    ```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*
+-->
+
+## Reverted `coreutils` to fix `cargo install` [[toc](#table-of-contents)]
+
+Bumping `coreutils` to 0.1.0 broke `cargo install nu`.
+The new version requires the `PROJECT_NAME_FOR_VERSION_STRING` environment variable at build time, which we had set in our `.cargo/config.toml`.
+
+Unfortunately, `cargo publish` does **not** ignore that file, which is considered [a bug in Cargo](https://github.com/rust-lang/cargo/issues/14001).
+As a result, we published a version that couldn't be installed without setting that env var manually.
+
+[The `coreutils` team is running into this too](https://github.com/uutils/coreutils/issues/7992).
+
+For now, we've reverted [#15896](https://github.com/nushell/nushell/pull/15896) in [#15932](https://github.com/nushell/nushell/pull/15932).
+We'll bump `coreutils` again once they’ve sorted out a fix.
+
+# Full changelog [[toc](#table-of-contents)]
+
+|author|title|link|
+|-|-|-|
+|[@cptpiepmatz](https://github.com/cptpiepmatz)|Revert "update nushell to use coreutils v0.1.0 crates (#15896)"|[#15932](https://github.com/nushell/nushell/pull/15932)|
+
+<!-- TODO:
+    - `use nu_scripts/make_release/release-note/notes.nu *`
+    - run `list-prs --milestone v0.105.1 | pr-table`
+    - paste the output here
+
+Afterwards, go through each PR and classify it as one of the following:
+    - A user-facing change. These PRs should go into the `# Changes` section.
+    - A plugin-facing change. These PRs should go in `# Notes for plugin developers`. Some plugin-facing changes might also be a user-facing change and vice versa.
+    - A documentation improvement, error message improvement, refactoring PR, clippy fix, typo fix, etc. These PRs go into the `# Hall of fame`. You can just copy the table row in this section and paste it to the `# Hall of fame` section above. Note that major refactorings may warrant a section in `# Highlights`.
+    - Dependabot PRs and version bumps should be ignored. They will only be mentioned in `# Full changelog`.
+-->