Add a parse method wrapper and caching to fix AoT compilation by @EdwardCooke in #1103 BREAKING CHANGE This is a breaking change in the TypeInspectorSkeleton class and the ITypeInspector interface by adding 2 methods . Quick fix to resolve those breaking changes in your own custom TypeInspector is to return false on the HasParseMethod method and return null or throw an exception on the Parse method.
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [YamlDotNet](https://github.com/aaubry/YamlDotNet/wiki) ([source](https://github.com/aaubry/YamlDotNet)) | nuget | major | `17.1.0` → `18.0.0` |
---
### Release Notes
<details>
<summary>aaubry/YamlDotNet (YamlDotNet)</summary>
### [`v18.0.0`](https://github.com/aaubry/YamlDotNet/releases/tag/v18.0.0): Release 18.0.0
#### What's Changed
- Add a parse method wrapper and caching to fix AoT compilation by [@​EdwardCooke](https://github.com/EdwardCooke) in [#​1103](https://github.com/aaubry/YamlDotNet/pull/1103)
**BREAKING CHANGE** This is a breaking change in the `TypeInspectorSkeleton` class and the `ITypeInspector` interface by adding 2 methods . Quick fix to resolve those breaking changes in your own custom TypeInspector is to return false on the HasParseMethod method and return null or throw an exception on the Parse method.
**Full Changelog**: <https://github.com/aaubry/YamlDotNet/compare/v17.1.0...v18.0.0>
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- 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.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xOTEuMiIsInVwZGF0ZWRJblZlciI6IjQzLjE5Ny4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Automation review 2026-05-26: not safe for unattended merge.
Breaking changes / compatibility concerns:
This updates YamlDotNet from 17.1.0 to 18.0.0.
Upstream v18.0.0 has an explicit breaking change around TypeInspectorSkeleton / ITypeInspector.
This repo has no Gitea workflow or PR-head CI status.
Are we affected?
Unlikely but not proven. I did not find usage of those extension points, but the app does use YAML serialization paths.
Risk:
Medium due to no CI: restore/build may pass, but YAML frontmatter/summary serialization could regress silently.
Professional recommendation:
Validate restore/build/tests plus YAML serialization smoke paths, then merge manually if those pass.
Automation review 2026-05-26: not safe for unattended merge.
Breaking changes / compatibility concerns:
- This updates `YamlDotNet` from 17.1.0 to 18.0.0.
- Upstream v18.0.0 has an explicit breaking change around `TypeInspectorSkeleton` / `ITypeInspector`.
- This repo has no Gitea workflow or PR-head CI status.
Are we affected?
- Unlikely but not proven. I did not find usage of those extension points, but the app does use YAML serialization paths.
Risk:
- Medium due to no CI: restore/build may pass, but YAML frontmatter/summary serialization could regress silently.
Professional recommendation:
- Validate restore/build/tests plus YAML serialization smoke paths, then merge manually if those pass.
Status update 2026-05-26: rechecked by Codex automation. Still blocked. Server-side main now has a PR workflow, but the Renovate branch still has no matching PR-head run and needs rebase/retry. YamlDotNet v18 breaking changes likely do not hit custom type inspectors here, but YAML frontmatter behavior should be covered by fresh CI/smoke validation before merge.
Status update 2026-05-26: rechecked by Codex automation. Still blocked. Server-side main now has a PR workflow, but the Renovate branch still has no matching PR-head run and needs rebase/retry. YamlDotNet v18 breaking changes likely do not hit custom type inspectors here, but YAML frontmatter behavior should be covered by fresh CI/smoke validation before merge.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
17.1.0→18.0.0Release Notes
aaubry/YamlDotNet (YamlDotNet)
v18.0.0: Release 18.0.0What's Changed
BREAKING CHANGE This is a breaking change in the
TypeInspectorSkeletonclass and theITypeInspectorinterface by adding 2 methods . Quick fix to resolve those breaking changes in your own custom TypeInspector is to return false on the HasParseMethod method and return null or throw an exception on the Parse method.Full Changelog: https://github.com/aaubry/YamlDotNet/compare/v17.1.0...v18.0.0
Configuration
📅 Schedule: (UTC)
🚦 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.
Automation review 2026-05-26: not safe for unattended merge.
Breaking changes / compatibility concerns:
YamlDotNetfrom 17.1.0 to 18.0.0.TypeInspectorSkeleton/ITypeInspector.Are we affected?
Risk:
Professional recommendation:
Status update 2026-05-26: rechecked by Codex automation. Still blocked. Server-side main now has a PR workflow, but the Renovate branch still has no matching PR-head run and needs rebase/retry. YamlDotNet v18 breaking changes likely do not hit custom type inspectors here, but YAML frontmatter behavior should be covered by fresh CI/smoke validation before merge.
97adceffddto8dc5bb25bf8dc5bb25bfto6c8d2ea0bd6c8d2ea0bdto7a5cf7972d