Tags: maxim-uvarov/nushell
Tags
Bump version to `0.78.0` (nushell#8715) # Description Version bump for the `0.78.0` Start to include the version with our `default_config.nu` and `default_env.nu` # Checklist - [x] reedline - [ ] release notes
Bump to `0.77.1` development version (nushell#8453) # Description Either to be used in an emergency point release or to indicate development builds in the `version` command
Bump version for `0.76.0` release (nushell#8121) Before landing: - [x] `reedline 0.16.0` is out and pinned. - [x] all fixes and features necessary are landed. In the meantime: - [ ] feed the release notes with relevant features and breaking changes
Version bump for `0.75` release (nushell#7902) - [x] Are we ready for the release - [x] Upgrade to upcoming `reedline 0.15`
Commit the lockfile for 0.74 (nushell#7719) Was missed in nushell#7718
bump to 0.73 (nushell#7542) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ # User-Facing Changes _(List of all changes that impact the user experience here. This helps us keep track of breaking changes.)_ # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
Update release script to nu v0.71 and use ubuntu-20.04 to build nu bi… …nary (nushell#7290) # Description 1. Update nu to v0.71 for release script 2. Remove the usage of `set-output` see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ 3. Use `ubuntu-20.04` instead of `ubuntu-latest` to fix nushell#7282 To check the workflow running result see: https://github.com/hustcer/nu-release/actions/runs/3588720720/jobs/6040412953 # User-Facing Changes _(List of all changes that impact the user experience here. This helps us keep track of breaking changes.)_ # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
PreviousNext