chore(deps): update dependency yamldotnet to v12
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| yamldotnet (source) | nuget | major | 11.2.1 -> 12.0.1 |
Release Notes
aaubry/YamlDotNet
v12.0.1
-
Update GitGub token
-
Merge pull request #707 from EdwardCooke/ec-updategithubtemplates
Removed on-hold notices from the issue templates -
Merge pull request #710 from lahma/fix-key-indicator
Fix block entry indicator check
v12.0.0
-
Merge pull request #623 from jairbubbles/add-tostring-on-yamlexception
Do not include the Start / End in the YamlException message- Make sure the constructors are consistant so that Message only contains the original message
- Add ToString to include Start / End
-
Merge pull request #624 from jairbubbles/include-start-end-in-exceptions-thrown-by-type-in
Include start / end in exceptions thrown by type inspector -
Merge pull request #626 from willson556/bugfix/extra-newline
Fix #361 - Extra Windows newline in folded scalar. -
Adapt the code and project structure to easuly build with Unity
-
Merge pull request #646 from lahma/string-builder-pool
Introduce StringBuilderPool -
Merge pull request #648 from lahma/avoid-params-array-in-hash-code
Avoid extra allocations in YamlScalarNode GetHashCode -
Merge pull request #647 from lahma/struct-mark
Change Mark to be readonly struct -
Merge pull request #649 from lahma/add-benchmark
Add YamlDotNet.Benchmark -
Update NuGet API key
-
Link to the discussion about the status of the project
-
Update README.md
-
Merge pull request #693 from EdwardCooke/ec-updates
VS 2022, Unit Tests and fixes -
Merge pull request #696 from aaubry/JG-update-readme
Remove the hint that this project is on hold -
Merge pull request #695 from EdwardCooke/ec-fix637-numberformat
G17 was creating issues with doubles and floats -
Merge pull request #659 from dmitry-ra/fix-issue-638
Fix #638: Parser hangs on stream of%Y -
Merge pull request #698 from EdwardCooke/ec-643-setonlyproperties
Allow set only properties during deserialization -
Merge pull request #697 from EdwardCooke/ec-fix658-releasenotes
Change the release notes link to use github releases -
Merge pull request #699 from EdwardCooke/ec-roundtripnulls
Allow quoting of specialized strings like null/true/false/numbers etc -
Merge pull request #701 from JoC0de/fix-nuget-package-spec
fixup nuget package spec -
Merge pull request #664 from krisrok/fix/comment-indents
Fix/comment indents (and other comment-related issues) -
Merge pull request #700 from EdwardCooke/ec-fix684-blockscalarkeys
Block scalars can be keys too -
Merge pull request #702 from EdwardCooke/ec-fix673-longminvaluedeserialize
Make long.minvalue deserialize -
Merge pull request #704 from aaubry/fix-prereleases-on-artifactory
Ensure that pre-releases are always in lower case
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, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:
- The detector detects more or fewer components than before
- The detector generates different parent/child graph relationships than before
- The detector generates different
devDependenciesvalues than before
If none of the above scenarios apply, feel free to ignore this comment 🙂
👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:
- The detector detects more or fewer components than before
- The detector generates different parent/child graph relationships than before
- The detector generates different
devDependenciesvalues than before
If none of the above scenarios apply, feel free to ignore this comment 🙂
The breaking change is dropping support for .NET Standard. As we on .NET 6 this doesn't affect us.