- Removes the note about installing the dataframes feature.
- Moves the command changes section to the top level, renames some sub
sections, and adds some more sub sections.
- Moves and simplifies the hall of fame.
This PR adds two [`cargo hack`](https://github.com/taiki-e/cargo-hack)
commands to the release process to check for errors due to combination
of features. The first one will run `cargo check` on each crate multiple
times over, toggling different combinations of features each time. This
is to check for compilation errors regarding missing imports, etc. The
second command will run `cargo build` for each crate separately (with
default features) to check for build errors (from `build.rs` or
whatever).
Using the [error](https://github.com/nushell/nushell/pull/11786) from
the 0.90.0 publishing as a test, the first command does indeed find the
compilation error.
In the future, we should probably put these commands into a manually
triggered CI job so that they will be run on multiple platforms.
Also, this PR cleans up `nu_release.nu` a little bit.
* add `bump-version.nu` to bump a version automatically
* mention `bump-version` in the release guide insted of `sd`
* remove the Note about `sd`ing the `Cargo.lock` file
* break very long lines
* find and replace in the `.nu` config files only
* fix the `str expand` command call for windows
it appears to not work properly with the `\` introduced by `path join`.
* update the `make_release/Readme.md` with the whole process
* complete the release process of `reedline` and `nu-ansi-term`
* make the 0 section title more clear
* make the Git remotes more general and be clear about that
* use `v0.xx.0` tags for both `reedline` and `nu-ansi-term`
* move "create release PR" script to `make_release/release-note/`
* move "since last release" script to `make_release/release-note/`
* add a script to list contributions for the release note
* rewrite `since_last_release` to use `list-merged-prs`
This commit also makes the script executable.
* update the `make_release/` readme
* add the commands to run to the release note template
* rename `since_last_release.nu` to `get-full-changelog`
* move the release note PR template to a standalone file
* add another section to inspect Nushell PRs to write changelogs
* fix the name of the command inside it's own doc
* add a script to create the release note PR of the website
* make the script executable
* pass the PR data to the open-pr command in a record
* add instructions to run the script in the readme
* move the core of the instructions to the help of the script
* refactor the repo cleaning in a tool command
* link to the repo if the user is not logged into `gh`
we also clean the repo in that case.
