build(deps): bump yamlpath from 3.9.0 to 3.9.1 in /yaml

[dependabot]

Bumps yamlpath from 3.9.0 to 3.9.1.

Release notes

Sourced from yamlpath's releases.

3.9.1

Enhancements:

• The yaml-validate, yaml-paths, yaml-diff, and yaml-merge command-line tools now accept -j|--json-multi-doc to parse adjacent JSON documents (including NDJSON/JSONL and concatenated JSON roots) as multi-document inputs. This was previously supported automatically by happenstance before adding light input validation to support frontmatter YAML parsing in Markdown documents for version 3.9.0. You do NOT need to use this new option for single-document JSON input; it is only necessary for multi-document JSON input. That said, it is harmless to use this new option universally for all JSON input. Thanks go to https://github.com/deepakbshetty for requesting this enhancement via wwkimball/yamlpath#239.

Bug Fixes:

• Mitigate ruamel.yaml issue 351 via workaround until the upstream bug is fixed. The workaround results in the expected round-trip edit, preserving the comments and new-lines which previously caused ruamel.yaml to stack-dump when those comments or new-lines within YAML files were near aliased hash keys. See https://sourceforge.net/p/ruamel-yaml/tickets/351/ for details.

Changelog

Sourced from yamlpath's changelog.

3.9.1 Enhancements:

• The yaml-validate, yaml-paths, yaml-diff, and yaml-merge command-line tools now accept -j|--json-multi-doc to parse adjacent JSON documents (including NDJSON/JSONL and concatenated JSON roots) as multi-document inputs. This was previously supported automatically by happenstance before adding light input validation to support frontmatter YAML parsing in Markdown documents for version 3.9.0. You do NOT need to use this new option for single-document JSON input; it is only necessary for multi-document JSON input. That said, it is harmless to use this new option universally for all JSON input. Thanks go to https://github.com/deepakbshetty for requesting this enhancement via wwkimball/yamlpath#239.

Bug Fixes:

• Mitigate ruamel.yaml issue 351 via workaround until the upstream bug is fixed. The workaround results in the expected round-trip edit, preserving the comments and new-lines which previously caused ruamel.yaml to stack-dump when those comments or new-lines within YAML files were near aliased hash keys. See https://sourceforge.net/p/ruamel-yaml/tickets/351/ for details.

Commits

• 666504c Merge pull request #241 from wwkimball/development
• 1ec209b Bump version to 3.9.1
• 378310b Merge master into development with scoped dependency-only sync
• e510b1f Bump pytest from 8.2.2 to 9.0.3 in /requirements/test-tools (#238)
• 8aa4933 Mention fix for ruamel.yaml issue 351
• 2b91fa2 Bugfix/239 (#240)
• f75ab6d Disable pip caching due to persistent HTTP cache corruption warnings
• 3e53cba Protect tests against breaking pylint changes
• deec3d9 Mitigate ruamel.yaml issue 351 via workaround
• b29f859 Fix missed mypy error
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)