Repository navigation
Bump YamlDotNet from 16.3.0 to 18.1.0 - #391
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
the
dependencies
dependabot
Bot
added
the
dependencies
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the NuGet dependency management to use YamlDotNet 18.1.0 (from 11.2.1) via the central Packages.props file, bringing in upstream security and behavioral changes that will affect YAML parsing/deserialization across the language server and sync components.
Changes:
- Bump
YamlDotNetfrom11.2.1to18.1.0in central package versions (src/Packages.props).
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| <PackageReference Update="System.CommandLine" Version="2.0.0-beta4.22272.1" /> | ||
| <PackageReference Update="System.Text.Json" Version="$(AspNetCoreVersion)" /> | ||
| <PackageReference Update="YamlDotNet" Version="11.2.1" /> | ||
| <PackageReference Update="YamlDotNet" Version="18.1.0" /> |
--- updated-dependencies: - dependency-name: YamlDotNet dependency-version: 18.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/nuget/src/main/YamlDotNet-18.1.0
branch
from
September 24, 2026 01:48
0c6e0e5 to
3f789cd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updated YamlDotNet from 16.3.0 to 18.1.0.
Release notes
Sourced from YamlDotNet's releases.
18.1.0
What's Changed
New Contributors
Full Changelog: aaubry/YamlDotNet@v18.0.0...v18.1.0
18.0.0
What'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: aaubry/YamlDotNet@v17.1.0...v18.0.0
17.1.0
What's Changed
There was a potential breaking change for large yaml files in the MergingParser. You may need to specify the optional parameter for maximum events to be processed. It default to 100k events which is a very large yaml file.
Full Changelog: aaubry/YamlDotNet@v17.0.0...v17.1.0
17.0.0
What's Changed
New Contributors
Full Changelog: aaubry/YamlDotNet@v16.3.0...v17.0.0
Commits viewable in compare view.