eemeli/yaml (yaml)
### [`v2.5.0`](https://togithub.com/eemeli/yaml/compare/v2.4.5...v2.5.0)
[Compare Source](https://togithub.com/eemeli/yaml/compare/v2.4.5...v2.5.0)
### [`v2.4.5`](https://togithub.com/eemeli/yaml/releases/tag/v2.4.5)
[Compare Source](https://togithub.com/eemeli/yaml/compare/v2.4.4...v2.4.5)
- Improve tab handling ([#553](https://togithub.com/eemeli/yaml/issues/553), yaml-test-suite tests [DK95](https://togithub.com/yaml/yaml-test-suite/blob/main/src/DK95.yaml) & [Y79Y](https://togithub.com/yaml/yaml-test-suite/blob/main/src/Y79Y.yaml))
### [`v2.4.4`](https://togithub.com/eemeli/yaml/releases/tag/v2.4.4)
[Compare Source](https://togithub.com/eemeli/yaml/compare/v2.4.3...v2.4.4)
With special thanks to [@RedCMD](https://togithub.com/RedCMD) for finding and reporting all of the following:
- Allow comment after top-level block scalar with explicit indent indicator ([#547](https://togithub.com/eemeli/yaml/issues/547))
- Allow tab as indent for line comments before nodes ([#548](https://togithub.com/eemeli/yaml/issues/548))
- Do not allow tab before block collection ([#549](https://togithub.com/eemeli/yaml/issues/549))
- In flow collections, allow `[]{}` immediately after `:` with plain key ([#550](https://togithub.com/eemeli/yaml/issues/550))
- Require indentation for `?` explicit-key contents ([#551](https://togithub.com/eemeli/yaml/issues/551))
- Require indentation from block scalar header & flow collections in mapping values ([#553](https://togithub.com/eemeli/yaml/issues/553))
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 contains the following updates:
2.4.3->2.5.0Release Notes
eemeli/yaml (yaml)
### [`v2.5.0`](https://togithub.com/eemeli/yaml/compare/v2.4.5...v2.5.0) [Compare Source](https://togithub.com/eemeli/yaml/compare/v2.4.5...v2.5.0) ### [`v2.4.5`](https://togithub.com/eemeli/yaml/releases/tag/v2.4.5) [Compare Source](https://togithub.com/eemeli/yaml/compare/v2.4.4...v2.4.5) - Improve tab handling ([#553](https://togithub.com/eemeli/yaml/issues/553), yaml-test-suite tests [DK95](https://togithub.com/yaml/yaml-test-suite/blob/main/src/DK95.yaml) & [Y79Y](https://togithub.com/yaml/yaml-test-suite/blob/main/src/Y79Y.yaml)) ### [`v2.4.4`](https://togithub.com/eemeli/yaml/releases/tag/v2.4.4) [Compare Source](https://togithub.com/eemeli/yaml/compare/v2.4.3...v2.4.4) With special thanks to [@RedCMD](https://togithub.com/RedCMD) for finding and reporting all of the following: - Allow comment after top-level block scalar with explicit indent indicator ([#547](https://togithub.com/eemeli/yaml/issues/547)) - Allow tab as indent for line comments before nodes ([#548](https://togithub.com/eemeli/yaml/issues/548)) - Do not allow tab before block collection ([#549](https://togithub.com/eemeli/yaml/issues/549)) - In flow collections, allow `[]{}` immediately after `:` with plain key ([#550](https://togithub.com/eemeli/yaml/issues/550)) - Require indentation for `?` explicit-key contents ([#551](https://togithub.com/eemeli/yaml/issues/551)) - Require indentation from block scalar header & flow collections in mapping values ([#553](https://togithub.com/eemeli/yaml/issues/553))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 was generated by Mend Renovate. View the repository job log.