The primary reason for this release is a change to the pre-commit hook that might be breaking to some users.
Features
pre-commit hook no longer specifies filetypes
The expectation for yamlfmt is to be run in a working directory of many different filetypes, and to configure what you as a user want the tool to run on based on configuration (file extensions, doublestar patterns, etc). The hook no longer specifies types: [yaml] like it used to. You can restore this behaviour by overriding it in your pre-commit config like so:
- repo: https://github.com/google/yamlfmt
rev: v0.18.0
hooks:
- id: yamlfmt
types: [yaml]However, you will likely have a better experience by reconfiguring yamlfmt to match the intended experience.
Default usage message on misuse of command
If you use the command yamlfmt with no arguments, and no config is discovered, the tool will now output a default usage message to indicate to the user how to properly use the command.