Releases: rliebz/tusk
Releases · rliebz/tusk
v0.7.1
v0.7.0
0.7.0 (2024-08-07)
Added
- Arguments may now specify a
type
, which works the same way as options. - Boolean options may now be rewritten into strings using
rewrite
. - Environment variables are now automatically parsed from
.env
files. - Additional environment variable files can be specified with
env-file
.
Fixed
- Arguments and options are now properly validated when passed to sub-tasks.
- Short names may no longer be provided for private options.
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
0.6.0 (2020-05-16)
Added
- The interpreter used for running commands can now be configured using the
top-levelinterpreter
clause in the YAML configuration.
Changed
- The interpreter now allows for specifying an arbitrary command and series of
arguments, so interpreters likenode
orruby
that happen to use a flag
other than-c
may be specified. - The interpreter settings now also apply to commands run as part of
when
and
option
clauses.
Removed
- BREAKING: To avoid inadvertantly picking up unrelated shell settings, the
environment variableSHELL
is no longer considered an override for the
command interpreter.
v0.5.2
v0.5.1
v0.5.0
0.5.0 (2019-12-05)
Added
- The
command
clause now accepts aprint
option to override the command
text that is printed to screen. - The
command
clause now acccepts adir
option to change the working
directory for that command.
Changed
- The
command
clause now has a longer form, where string literals now map to
theexec
field. This longer form allows additional options such asprint
to be specified in a command when necessary while maintaining backward
compatibility.
Fixed
- BREAKING: Unspecified fields in the YAML or duplicate map keys should
more consistently raise errors when parsing. Sometusk.yml
files with
issues that were treated as valid in previous versions may no longer be
considered valid.
Removed
- BREAKING: Setting environment variables with
environment
has been
removed in favor ofset-environment
.