Update dependency yamlfmt to v0.12.0 #133
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.11.0
->0.12.0
Release Notes
google/yamlfmt (yamlfmt)
v0.12.0
Compare Source
Output Format Release
I have unfortunately been dealing with a long-running health problem that has made it difficult to do much work on this or any projects for the past couple of months. I did manage to get together some small features and fixes worth noting.
Features
Output Format
You can now choose different output formats for lint/dry run. The first alternate output format added is
line
, which makes it so instead of the full detailed output, yamlfmt outputs single lines for each file with formatting differences. This should allow for easier integration into tools like reviewdog. I have never used that tool, but if anyone is able to get an integration working, feel free to open a Discussion thread about it and let me know!More config file name options
Last release, I added configuration file naming options to have the yaml extension, i.e.
yamlfmt.yaml
andyamlfmt.yml
. The way I did that made it so you couldn't have config files with extension also be hidden. That is resolved now, so you can have.yamlfmt.yaml
etc.Bug Fixes
Don't write files if there is no diff
Previously, yamlfmt would always write all files set for formatting even when there would be no change. This meant the edited date of the file was always being updated even though nothing was meant to change. That should not happen anymore.
Fix
-global_conf
not working as documentedThe
-global_conf
flag was not working as documented in the last release. If there was a local config,-global_conf
would end up being ignored and the local config would be used first. This was not the intended functionality and it has been fixed.Contributors
Thanks @kiliantyler for the catching the global configuration bug and opening a fix for it!
1k stars!
Thank you very much for over 1000 stars on GitHub! I appreciate the support, and I hope the tool continues to be useful to the community!
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.
This PR has been generated by Mend Renovate. View repository job log here.