chore(deps): update dependency yamldotnet to 18.1.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
YamlDotNet (source)	18.0.0 → 18.1.0

---

Release Notes

aaubry/YamlDotNet (YamlDotNet)

v18.1.0: Release 18.1.0

What's Changed

• Use NET 10 with benchmarks by @​mcraiha in #​1099
• Revert package upgrades by @​EdwardCooke in #​1104
• Added default maximum recursion level of 130 (max when using defaults on Windows/.net8) by @​EdwardCooke in #​1110
• Static deserializer builder needed the default maximum recursion by @​EdwardCooke in #​1111

New Contributors

• @​mcraiha made their first contribution in #​1099

Full Changelog: aaubry/YamlDotNet@v18.0.0...v18.1.0

Breaking

• Maximum depth of yaml files is now 130 by default. If you need higher you will need to adjust the maximum yaml depth. Going above 130 runs the risk of stack overflow exceptions when any exception happens inside of the deserialization

---

Configuration

📅 Schedule: (in timezone Europe/London)

• Branch creation
  • "before 8am"
• 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.

[gemini-code-assist]

Code Review

This pull request updates the YamlDotNet package version from 18.0.0 to 18.1.0 in Directory.Packages.props. The review feedback highlights that this upgrade introduces a default maximum recursion limit of 130, which may cause deserialization failures for deeply nested YAML configurations, and recommends configuring an explicit limit if necessary.

[gemini-code-assist]

The upgrade to YamlDotNet 18.1.0 introduces a default maximum recursion limit of 130. For very large or deeply nested YAML configurations, this can cause deserialization to fail with an exception. If the generator processes complex, deeply nested YAML files, configure the parser/deserializer with an explicit maximum recursion limit to prevent unexpected runtime failures.

References

1. When upgrading third-party dependencies, verify whether the codebase actually utilizes the specific interfaces or classes affected by breaking changes before implementing suggested fixes.