Releases: xt0rted/dotnet-run-script
Releases · xt0rted/dotnet-run-script
v0.6.0
v0.5.0
v0.4.0
Note
This version drops support for .NET 5 which is no longer supported, but it will continue to work with .NET 5 SDKs.
Added
- Ability to run multiple scripts in a single call (e.g.
dotnet r build test pack) (#10) - Support for globbing in script names (e.g
dotnet r test:*will matchtest:unitandtest:integration) (#79)
Updated
- Bumped
System.CommandLinefrom 2.0.0-beta3.22114.1 to 2.0.0-beta4.22272.1 - Bumped
System.CommandLine.Renderingfrom 0.4.0-alpha.22114.1 to 0.4.0-alpha.22272.1
v0.3.0
v0.2.0
Note
This version broke conditional script execution (cmd1 && cmd2) incmd.exe
Added
- Force color output with the
DOTNET_SYSTEM_CONSOLE_ALLOW_ANSI_COLOR_REDIRECTIONenvironment variable.- Note: this tool with output color on all platforms including when output is redirected, but the dotnet cli only supports this on Unix platforms currently. This means script results might not be colored in places like GitHub Actions build logs when using the Windows VMs.
- Added
-valias to enable verbose output.
Fixed
- Escape arguments for non-cmd shells
- Quote additional arguments passed after
-- - Escape scripts with
^passed tocmd.exe
Updated
- Switched from actions/setup-dotnet to xt0rted/setup-dotnet
v0.1.0
- Run scripts with
dotnet r ... - Uses
cmdon Windows andshon Linux - Support for
preandpostscripts - Support for setting a custom shell such as
pwsh- Set via the
scriptShellglobal.json setting - Set via the
--script-shellparameter
- Set via the
- Built-in
envcommand to list available environment variables - Flow parameters after
--to the running script - Skip commands that aren't found with the
--if-presentparameter