v0.5.1

0.5.1 - 2023-03-11

• Added a new labels feature. This allows you to group commands in your config file by assigning one or more labels in their config. Then when running precious, you can run commands with a specific label: precious lint --label some-label --all. Suggested by Greg Oschwald. Addresses #8.

v0.5.0

• The --git flag did not include any staged files, only files that were modified but not staged. It now includes all modified files, whether or not they're staged.

v0.4.1

• The previous release didn't handle all of the old config keys correctly. If just run_mode or chdir was set, but not both, it may not have replicated the behavior of precious v0.3.0 and earlier with the same settings.

v0.4.0

• This release has huge changes to how commands are invoked. The old run_mode and chdir configuration keys have been deprecated. In the future, using these will cause precious to print a warning, and later support will be removed entirely. See the documentation for more details. There are also some docs on upgrading from previous versions.
• Fixed path handling for --git and --staged when the project root (the directory containing the precious config file) is a subdirectory of the git repo root. Previously this would just attempt to run against incorrect paths.
• Precious now supports patterns starting with ! in include and exclude keys. This allow you to exclude the given pattern, even if matches previous rules in the list. See the Git docs on .gitignore patterns for more details. Fixes GH #39.
• When run in GitHub Actions, precious will now emit GitHub annotations for linting errors.

v0.3.0

• The expect_stderr config parameter has been replaced by ignore_stderr. This new parameter accepts one or more strings, which are turned into regexes. If the command's stderr output matches any of the regexes then it is ignore. The old expect_stderr parameter will continue to work for now, but it is no longer documented. To replicate the old behavior simply set ignore_stderr = ".*".

v0.2.3

• When given the , --git, --staged, or --staged-with-stash flags, precious would error out if all the relevant files were excluded. This is likely to break commit hooks so this is no longer an error. However, if given either the --all flag or an explicit list of files, it will still error if all of them are excluded.

v0.2.2

• Added a --command flag to the lint and tidy subcommands. If this is passed, then only the command with the given name will be run. This addresses #31, requested by Olaf Alders.

v0.2.1

• The way precious works when run in a subdirectory of the project root has changed.
  • When given the --all, --git, --staged, or --staged-with-stash flags, it will look for all files in the project, regardless of what directory you execute precious in.
  • When given relative paths to files it will do the right thing. Previously it would error out with "No such file or directory". Reported by Greg Oschwald. Fixes #29.

v0.2.0

• The --staged mode no longer tries to stash unstaged content before linting or tidying files. This can cause a number of issues, and shouldn't be the default. There is a new --staged-with-stash mode that provides the old --staged behavior. Reported by Greg Oschwald. Fixes #30.

v0.1.7

• If a command sent output to stdout, but not stderr, and exited with an unexpected error code, then the output to stdout would not be shown by precious in the error message. Reported by Greg Oschwald. GH #28.