Skip to content

Commit c0bd8ad

Browse files
committed
Release notes for 0.101.0
Please add your new features and breaking changes to the release notes by opening PRs against the `release-notes-0.101.0` branch. ## TODO - [ ] look at interesting contributions - [ ] write all the sections - [ ] order the sections by interest - [ ] add the breaking changes - [ ] detail the breaking changes - [ ] add the full changelog - [ ] complete all the `TODO`s inside the release note - [ ] ... (PRs that need to land before the release, e.g. [deprecations](https://github.com/nushell/nushell/labels/deprecation) or [removals](https://github.com/nushell/nushell/pulls?q=is%3Apr+is%3Aopen+label%3Aremoval-after-deprecation))
1 parent f9748b6 commit c0bd8ad

File tree

1 file changed

+77
-0
lines changed

1 file changed

+77
-0
lines changed

blog/2024-12-24-nushell_0_101_0.md

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
---
2+
title: Nushell 0.101.0
3+
author: The Nu Authors
4+
author_site: https://twitter.com/nu_shell
5+
author_image: https://www.nushell.sh/blog/images/nu_logo.png
6+
excerpt: Today, we're releasing version 0.101.0 of Nu. This release adds...
7+
---
8+
<!-- TODO: complete the excerpt above -->
9+
10+
<!-- NOTE: start from the TODO all the way at the bottom (and sort of work your way up) -->
11+
12+
# Nushell 0.101.0
13+
14+
<!-- TODO: write this excerpt -->
15+
Today, we're releasing version 0.101.0 of Nu. This release adds...
16+
17+
# Where to get it
18+
19+
Nu 0.101.0 is available as [pre-built binaries](https://github.com/nushell/nushell/releases/tag/0.101.0) or from [crates.io](https://crates.io/crates/nu). If you have Rust installed you can install it using `cargo install nu`.
20+
21+
As part of this release, we also publish a set of optional plugins you can install and use with Nu. To install, use `cargo install nu_plugin_<plugin name>`.
22+
23+
# Table of contents
24+
25+
<!-- 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`. -->
26+
27+
# Highlights and themes of this release
28+
29+
<!-- NOTE: if you wanna write a section about a breaking change, when it's a very important one,
30+
please add the following snippet to have a "warning" banner :)
31+
> see [an example](https://www.nushell.sh/blog/2023-09-19-nushell_0_85_0.html#pythonesque-operators-removal)
32+
33+
```md
34+
::: warning Breaking change
35+
See a full overview of the [breaking changes](#breaking-changes)
36+
:::
37+
```
38+
-->
39+
<!-- NOTE: see https://vuepress.github.io/reference/default-theme/markdown.html#custom-containers
40+
for the list of available *containers*
41+
-->
42+
43+
# Changes
44+
45+
## Additions
46+
47+
## Breaking changes
48+
49+
## Deprecations
50+
51+
## Removals
52+
53+
## Bug fixes and other changes
54+
55+
# Notes for plugin developers
56+
57+
# Hall of fame
58+
59+
Thanks to all the contributors below for helping us solve issues, improve documentation, refactor code, and more! :pray:
60+
61+
| author | title | link |
62+
| ------------------------------------ | ----------- | ------------------------------------------------------- |
63+
| [@author](https://github.com/author) | ... | [#12345](https://github.com/nushell/nushell/pull/12345) |
64+
65+
# Full changelog
66+
67+
<!-- TODO:
68+
- `use nu_scripts/make_release/release-note/notes.nu *`
69+
- run `list-prs --milestone v0.101.0 | pr-table`
70+
- paste the output here
71+
72+
Afterwards, go through each PR and clasify it as one of the following:
73+
- A user-facing change. These PRs should go into the `# Changes` section.
74+
- 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.
75+
- 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`.
76+
- Dependabot PRs and version bumps should be ignored. They will only be mentioned in `# Full changelog`.
77+
-->

0 commit comments

Comments
 (0)