Skip to content

Releases: rliebz/tusk

v0.7.1

07 Aug 13:22
Compare
Choose a tag to compare

0.7.1 (2024-08-07)

Fixed

  • Updated go releaser action with necessary permissions.

v0.7.0

07 Aug 13:00
Compare
Choose a tag to compare

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

28 Sep 02:02
Compare
Choose a tag to compare

0.6.4 (2022-09-27)

Fixed

  • Improved handling of colons in bash completion.

v0.6.3

17 Feb 02:30
Compare
Choose a tag to compare

0.6.3 (2022-02-16)

Added

  • The quiet clause is now available for commands and tasks to quiet
    additional logging.

v0.6.2

27 Apr 00:42
Compare
Choose a tag to compare

0.6.2 (2021-04-26)

Added

  • Added fish completions.

Fixed

  • Fixed an issue where certain behavior might unintentionally run during
    tab completions.
  • Fixed an issue where XDG_DATA_HOME was respected incorrectly when installing
    bash completions.

v0.6.1

18 Aug 02:19
Compare
Choose a tag to compare

0.6.1 (2020-08-17)

Added

  • Commands to install and uninstall completion will now appear in the help
    documentation.

v0.6.0

16 May 12:52
Compare
Choose a tag to compare

0.6.0 (2020-05-16)

Added

  • The interpreter used for running commands can now be configured using the
    top-level interpreter clause in the YAML configuration.

Changed

  • The interpreter now allows for specifying an arbitrary command and series of
    arguments, so interpreters like node or ruby 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 variable SHELL is no longer considered an override for the
    command interpreter.

v0.5.2

26 Jan 05:09
Compare
Choose a tag to compare

0.5.2 (2020-01-26)

Added

  • The include clause is now available to include task definitions from other
    files.

v0.5.1

14 Jan 01:10
Compare
Choose a tag to compare

0.5.1 (2020-01-13)

Fixed

  • Completions now correctly escape ":" characters in command and flag names.

v0.5.0

05 Dec 12:25
Compare
Choose a tag to compare

0.5.0 (2019-12-05)

Added

  • The command clause now accepts a print option to override the command
    text that is printed to screen.
  • The command clause now acccepts a dir option to change the working
    directory for that command.

Changed

  • The command clause now has a longer form, where string literals now map to
    the exec field. This longer form allows additional options such as print
    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. Some tusk.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 of set-environment.