Releases: nur-taskrunner/nur
Releases · nur-taskrunner/nur
Release v0.1.16
What's Changed
- Add build github action by @ddanier in #11
- This means you will not be able to download pre-built binaries for this and every future release, see below
- Including a nice
.msi
installer for Windows 🥳
- Besides this change version
0.1.16
is the same as0.1.15
Full Changelog: v0.1.15...v0.1.16
Release 0.1.15
- Update
nu
to version0.92.1
Release 0.1.14
- BREAKING: Upgrade to nu shell
0.92.0
, as it was just released. See https://www.nushell.sh/blog/2024-04-02-nushell_0_92_0.html for details and the BREAKING changes in nu shell itself extra
feature is now enabled by default, following what nu shell did- BREAKING: Removed plugin support, as I never really used and tested this. Also nu shell 0.92.0 changes the plugin behaviour which meant the old implementation was broken. If I want to have plugins I will care more about this.
- nur "e2e" tests now also run on Windows, which tells me Windows support doesn't look bad at all (thanks to nu shell of course!)
Release 0.1.13
nur --version
andnur --help
are now allowed to run even if no project path was found, previous versions did only show an error
Release 0.1.12
- Added support to store nu files in
$nur.project-path/.nur
, this allows for:.nur/scripts/
to store scripts or modules in your project.nur/config.nu
to have anur
specific config per project (see https://www.nushell.sh/book/configuration.html).nur/env.nu
to have anur
specific env per project.nur/plugin/
to have a project specific plugin config (UNTESTED, SEE BELOW)
- Added some tests that actually run
nur
to check if everything is setup correctly (I call those "cli end to end tests") - Core is now formatted using
cargo fmt
- Release version not uses size optimised build for smaller executable (following the settings
nu
also uses) - BREAKING: The old path to store scripts/modules (
.nurscripts/
) has been replaces by.nur/scripts/
, please move your scripts accordingly - BREAKING: Removed
dataframe
from default profile, asnu
does not support this by default either - BUGFIX:
$nur
was not available whennurfile
was initially loaded, but only in tasks (/commands) - Initial draft of plugin support, not tested yet, use with caution (Only available when compiled with
plugin
feature flag)
WARNING: I'm not sure I will keep this!
Release 0.1.11
- Bugfix:
$env.NU_VERSION
now contains the correct version, was broken since0.1.7
- Updated my own
nurfile
to ensure this is kept up to date
Release 0.1.10
- Respect exit code of commands in tasks and output error when tasks did not finish successfully
Release 0.1.9
- Removed --debug and --config from default build
- "Task exited ok" is not shown in green to be more friendly
Others:
- Added linter + first tests - will also be run as GitHub actions
Release 0.1.8
- Add
.nurscripts
in$nur.project-path
toNU_LIB_DIRS,
, so you can put modules there. 😉
Release 0.1.7
- Upgrade to nu shell version
0.91.0
, see release notes: https://www.nushell.sh/blog/2024-03-05-nushell_0_91_0.html - Some docs updates