chore(deps): update pre-commit hook google/yamlfmt to v0.14.0

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
google/yamlfmt	repository	minor	v0.13.0 -> v0.14.0

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

---

Release Notes

google/yamlfmt (google/yamlfmt)

### [`v0.14.0`](https://redirect.github.com/google/yamlfmt/releases/tag/v0.14.0) [Compare Source](https://redirect.github.com/google/yamlfmt/compare/v0.13.0...v0.14.0) ### Shoutouts To The Community Release I have been in not the best health the last while, which is why this release took so long to cut. On the bright side, this release features more contributions from the community than from myself. Thank you to everyone who contributed! ### Features #### `strip_directives` `yaml.v3` does not support directives. The best thing to do would be to add some amount of support for directives, which I will do in the future just taking it as far as the parser not failing upon finding a directive. In the short term, I added a `hotfix` style feature that will strip the directives before formatting and put them back in. The feature is fraught with edge cases and only works reliably with directives at the top of the file. See the explanations I added in the [docs](https://redirect.github.com/google/yamlfmt/blob/main/docs/config-file.md#strip_directives). #### `gitignore_excludes` searches up the directory structure for the nearest `.gitignore` Arguably a fix, the `gitignore_excludes` feature will now look up the directory structure for the nearest `.gitignore` which unlocks monorepo usage patterns for `yamlfmt`. #### JSON schema The community has added a [JSON Schema](https://redirect.github.com/google/yamlfmt/blob/52c3b64ffcb1ad694aee768fd0969822c65b2b64/schema.json)! I'm calling it out in release notes, but this is not tied to yamlfmt releases in any way. If you have any fixes or improvements to make, they will not need to be tied to git tags being cut. I am not super familiar with JSON Schema; I will try my best not to break it and keep it up to date but I'm not gonna be great at addressing potential deeper issues with it. #### Validating releases with `cosign` The release artifacts now generate other artifacts that allow you to verify releases using the [`cosign` tool](https://redirect.github.com/sigstore/cosign). ### Fixes #### The `line_ending` setting in the `formatter` config is respected again This was a regression in v0.13.0 where I did some refactors to config discovery. I uncovered an edge case in my original code to handle the `line_ending` setting in the `formatter` block (vs the global version). This has been fixed in this release. #### `eof_newline` no longer panics on an empty file If the file was empty, the `eof_newline` feature would panic. Never thought of that! This has been fixed. ### Contributors [@​thiagowfx](https://redirect.github.com/thiagowfx) added the JSON Schema [@​Shion1305](https://redirect.github.com/Shion1305) fixed the `eof_newline` panic [@​dhth](https://redirect.github.com/dhth) added cosign support to releases [@​nikaro](https://redirect.github.com/nikaro) added .gitignore discovery I think this is the most contributors I've had in a release! Thank you everyone! ### Changelog (generated) - feat: introduce a json schema file for yamlfmt by [@​thiagowfx](https://redirect.github.com/thiagowfx) in [https://github.com/google/yamlfmt/pull/193](https://redirect.github.com/google/yamlfmt/pull/193) - 🐛 panic against empty file with eof_newline feature, resolves: [#​196](https://redirect.github.com/google/yamlfmt/issues/196) by [@​Shion1305](https://redirect.github.com/Shion1305) in [https://github.com/google/yamlfmt/pull/197](https://redirect.github.com/google/yamlfmt/pull/197) - fix: look for gitignore file until the git root by [@​nikaro](https://redirect.github.com/nikaro) in [https://github.com/google/yamlfmt/pull/200](https://redirect.github.com/google/yamlfmt/pull/200) - fix(json schema): remove additionalProperties any by [@​thiagowfx](https://redirect.github.com/thiagowfx) in [https://github.com/google/yamlfmt/pull/202](https://redirect.github.com/google/yamlfmt/pull/202) - Add JSON schema validity test by [@​braydonk](https://redirect.github.com/braydonk) in [https://github.com/google/yamlfmt/pull/203](https://redirect.github.com/google/yamlfmt/pull/203) - ci: sign checksum file with cosign by [@​dhth](https://redirect.github.com/dhth) in [https://github.com/google/yamlfmt/pull/207](https://redirect.github.com/google/yamlfmt/pull/207) - Clarify that cosign support will only be present starting from v0.14.0 by [@​braydonk](https://redirect.github.com/braydonk) in [https://github.com/google/yamlfmt/pull/212](https://redirect.github.com/google/yamlfmt/pull/212) - command: correctly propogate line_ending setting by [@​braydonk](https://redirect.github.com/braydonk) in [https://github.com/google/yamlfmt/pull/216](https://redirect.github.com/google/yamlfmt/pull/216) - Add feature `strip_directives` by [@​braydonk](https://redirect.github.com/braydonk) in [https://github.com/google/yamlfmt/pull/217](https://redirect.github.com/google/yamlfmt/pull/217) **Full Changelog**: https://github.com/google/yamlfmt/compare/v0.13.0...v0.14.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.