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: make_release/Readme.md
+5-11Lines changed: 5 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,19 +71,13 @@
71
71
> - edit the `nu_release.nu` script to start again where it failed
72
72
> - re-run the script
73
73
74
-
## 4. Publish the release note on the website
75
-
> **Note**
76
-
> the scripts have been written in such a way they can be run from anywhere
77
-
78
-
- [ ] inspect the merged PRs to write changelogs with `./make_release/release-note/list-merged-prs nushell/nushell`
79
-
- [ ] reorder sections by priority, what makes the most sense to the user?
80
-
- [ ] paste the output of `./make_release/release-note/list-merged-prs nushell/nushell --label pr:breaking-change --pretty --no-author` to the "*Breaking changes*" section
81
-
- [ ] make sure breaking changes titles are clear enough
82
-
- [ ] paste the output of `./make_release/release-note/get-full-changelog` to the "*Full changelog*" section
83
-
- [ ] mark as *ready for review* when uploading to *crates.io*
74
+
## 4. Publish the release notes on the website
75
+
76
+
- [ ] follow and finish the TODOs in the release notes file
77
+
- [ ] mark as ready for review when uploading to crates.io
84
78
- [ ] land when
85
79
- **fully uploaded** to *crates.io*
86
-
- **before** the *GitHub* release
80
+
- **before** the GitHub release
87
81
88
82
## 5. Publish the release on *GitHub*
89
83
- [ ] go to the draft release on the [release page](https://github.com/nushell/nushell/releases)
Copy file name to clipboardExpand all lines: make_release/release-note/template.md
+27-71Lines changed: 27 additions & 71 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@ excerpt: Today, we're releasing version {{VERSION}} of Nu. This release adds...
7
7
---
8
8
<!-- TODO: complete the excerpt above -->
9
9
10
-
# Nushell {{VERSION}}
10
+
<!-- NOTE: start from the TODO all the way at the bottom (and sort of work your way up) -->
11
11
12
-
Nushell, or Nu for short, is a new shell that takes a modern, structured approach to your command line. It works seamlessly with the data from your filesystem, operating system, and a growing number of file formats to make it easy to build powerful command line pipelines.
12
+
# Nushell {{VERSION}}
13
13
14
14
<!-- TODO: write this excerpt -->
15
15
Today, we're releasing version {{VERSION}} of Nu. This release adds...
@@ -21,33 +21,11 @@ Nu {{VERSION}} is available as [pre-built binaries](https://github.com/nushell/n
21
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
22
23
23
# Table of contents
24
-
-[_Highlights and themes of this release_](#highlights-and-themes-of-this-release-toc)
25
-
-[_Changes_](#changes-toc)
26
-
-[_Additions_](#additions-toc)
27
-
-[_Breaking changes_](#breaking-changes-toc)
28
-
-[_Deprecations_](#deprecations-toc)
29
-
-[_Removals_](#removals-toc)
30
-
-[_Bug fixes and other changes_](#bug-fixes-and-other-changes-toc)
31
-
-[_Notes for plugin developers_](#notes-for-plugin-developers-toc)
32
-
-[_Hall of fame_](#hall-of-fame-toc)
33
-
-[_Full changelog_](#full-changelog-toc)
34
-
<!-- TODO: please add links to the other sections here
35
-
36
-
the following command should help pre-generate a great deal of the table of content.
37
-
be careful with the format and false-positives :wink:
# Highlights and themes of this release [[toc](#table-of-content)]
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
+
51
29
<!-- NOTE: if you wanna write a section about a breaking change, when it's a very important one,
52
30
please add the following snippet to have a "warning" banner :)
53
31
> see [an example](https://www.nushell.sh/blog/2023-09-19-nushell_0_85_0.html#pythonesque-operators-removal)
@@ -62,60 +40,38 @@ As part of this release, we also publish a set of optional plugins you can insta
62
40
for the list of available *containers*
63
41
-->
64
42
65
-
# Changes[[toc](#table-of-content)]
43
+
# Changes
66
44
67
-
## Additions[[toc](#table-of-content)]
45
+
## Additions
68
46
69
-
## Breaking changes[[toc](#table-of-content)]
47
+
## Breaking changes
70
48
71
-
## Deprecations[[toc](#table-of-content)]
49
+
## Deprecations
72
50
73
-
## Removals[[toc](#table-of-content)]
51
+
## Removals
74
52
75
-
## Bug fixes and other changes[[toc](#table-of-content)]
53
+
## Bug fixes and other changes
76
54
77
-
<!-- NOTE: to start investigating the contributions of last release, i like to list them all in a raw table.
78
-
to achieve this, one can use the [`list-merged-prs` script from `nu_scripts`](https://github.com/nushell/nu_scripts/blob/main/make_release/release-note/list-merged-prs)
79
-
as follows:
55
+
# Notes for plugin developers
80
56
81
-
```nushell
82
-
use ./make_release/release-note/list-merged-prs
83
-
use std clip
57
+
# Hall of fame
84
58
85
-
let last_release_date = ^gh api /repos/nushell/nushell/releases
86
-
| from json
87
-
| into datetime published_at
88
-
| get published_at
89
-
| sort
90
-
| last
59
+
Thanks to all the contributors below for helping us solve issues, improve documentation, refactor code, and more! :pray:
91
60
92
-
let prs = list-merged-prs nushell/nushell $last_release_date
- run `list-prs --milestone v{{VERSION}} | 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`.
0 commit comments