v0.1.6

• All binaries now statically link musl instead of the system libc.
• Added a number of new platforms for released binaries: Linux ARM 32-bit and 64-bit, and macOS ARM 64-bit.

v0.1.5

• When a command unexpectedly prints to stderr the error message we print now includes both stdout and stderr from that command. Reported by Greg Oschwald. Fixes #26.

• When a command was configured with the run_mode as files and chdir as true, the paths passed to the command would still include parent directories. Reported by Greg Oschwald. Fixes #25.

v0.1.4

• Running precious with the --staged flag would exit with an error if a post-checkout hook wrote any output to stderr. It appears that any output from a hook to stdout ends up on stderr for some reason, probably related to git/git@e258eb4. Based on PR#24 by Olaf Alders. Fixes #23.

v0.1.3

• Relaxed some dependencies for the benefit of packaging precious for Debian. Implemented by Jonas Smedegaard.
• Added support for .precious.toml as a config name. Based on #21, by Olaf Alders. Fixes #13.

v0.1.2 - Command order is preserved and a test fix

• The order of commands in the config file is now preserved, and commands are executed in the order in which they appear in the config file. This addresses #12, requested by Olaf Alders.
• Fix the tests so that they set the default branch name when running git init, rather than setting this via git config. This lets anyone run the tests, whereas it was only safe to set this via git config in CI. This fixes #14, reported by Olaf Alders.

v0.1.1

• Fixed config handling of a global exclude key. The previous release did not handle a single string as that key's value, only an array.

v0.1.0

• The verbose and debugging level output now includes timing information on each linter and tidier that is run. This is helpful if you want to figure out why linting or tidying is slower than expected.

• Fixed a bug in the debug output. It was not showing the correct cwd for commands where chdir = true was set. It always showed the project root directory instead of the directory where the command was run. It was running these commands in the right directory. This was solely a bug in the debug output.

v0.0.11

• Fix a bug in 0.0.10 where when not running with --debug, precious would not honor the expect_stderr = true configuration, and would instead unconditionally treat stderr output as an error.

v0.0.10

• Errors are now printed out a bit differently, and in particular errors when trying to execute a command (not in the path, command fails unexpectedly, etc.) should be more readable now.
• When running any commands, precious now explicitly checks to see if the executable is in your PATH. If it's not it prints a new error for this case, as opposed to when running the executable produces an error. This partially addresses #10.

v0.0.9

• Added a --jobs (-j) option for all subcommands. This lets you limit how many parallel threads are run. The default is to run one thread per available core. Requested by Shane Warden. GH #7.
• Fix a bug where running precious in "git staged mode" (precious lint --staged) would cause breakage with merge commits that were the result of resolving a merge conflict. Basically, you'd get the commit but git would no longer know it was merging a commit, because precious was running git stash under the hood to only check the staged files, then git stash pop to restore things back to their original state. But runningit stash command. There's some discussion of this on Stack Overflow but apparently it's still an issue with git today. Reported by Carey Hoffman. GH #9.