Bump YamlDotNet from 4.1.0 to 5.0.0 in /Resizetizer

[dependabot[bot]]

Bumps YamlDotNet from 4.1.0 to 5.0.0.

Release notes

Sourced from YamlDotNet's releases.

Security issues and dropping legacy behaviors

/!\ This release fixes a security issue. It is strongly recommended to upgrade, mainly if you are parsing documents from sources that you do not trust.

Many thanks to Kurt Boberg, from the DocuSign Application Security Team, who identified this issue and provided feedback on mitigation strategies.

• Remove the legacy backwards-compatibe syntax that enabled to create Serializer and Deserializer directly then changing their configutation.
  In most cases, the calls to the constructors should be replaced by instantiations of SerializerBuilder and DeserializerBuilder. These can be configured at will, then used to create instances of (De)serializer. It is still possible to use the default constructors, if no configuration is needed.

• Drop support for specifying arbitrary type names in tags.
  Support for automatically resolving a fully qualified type name from a tag has been discontinued. That feature was poorly designed and not standard.
  During deserialization, each tag mapping must be explicitly registered. During serialization, when using the EnsureRoundtrip method, it is necessary to register tag mappings for each type that will require a tag, that is, any type that is used as the value of a property with a different declared type.

• Fix bug where deserialized values were not being converted to the destination type.

  var sut = new DeserializerBuilder()
      .WithTagMapping("!dbl", typeof(DoublyConverted))
      .Build();
  
  // The scalar "hello" will first be converted to DoublyConverted
  // then that value will be converted to int.
  var result = sut.Deserialize<int>("!dbl hello");
  
  Assert.Equal(5, result);
  

Add support for (de)serialization of System.Type

No release notes provided.

Cleanup the project

• Refactored the project and solution so that they load and build cleanly in VS2017.
• Reviewed the target platforms.
  • The currently supported platforms are now:
    • .NET Framework 4.5
    • .NET Framework 3.5
    • .NET Framework 2.0 (experimental)
    • .NET Standard 1.3
    • Unity Subset v3.5
  • The following platforms are no longer supported:
    • Profile259 (please upgrade to netstandard)

... (truncated)

Changelog

Sourced from YamlDotNet's changelog.

Release notes

Release 8.0.0

New features and improvements

• Change the default value handling behavior. Fixes #427
  This is a breaking change to the default behaviour of the serializer, which will now always emit null and default values.
  It is possible to configure this behaviour by using the ConfigureDefaultValuesHandling method on SerializerBuilder.

  More details are available in the documentation.

• Add default implementations for the following non-generic collections to DefaultObjectFactory:

  • IEnumerable
  • ICollection
  • IList
  • IDictionary

• Remove obsolete and unused SerializationOptions enum. Fixes #438

• Throw descriptive exceptions when using the "linq" methods of YamlNode. Relates to #437

Bug fixes

• Never emit document end indicator on stream end. Fixes #436
• Fix exception when deserializing an interface. Fixes #439

Previous releases

• 7.0.0
• 6.1.2
• 6.1.1
• 6.0.0
• 5.4.0
• 5.3.1
• 5.3.0
• 5.2.1
• 5.2.0
• 5.1.0
• 5.0.0
• 4.3.2
• 4.3.1
• 4.3.0
• 4.2.4
• 4.2.3
• 4.2.2
• 4.2.1
• 4.2.0
• 4.1.0
• 4.0.0
• 3.9.0
• 3.8.0
• 3.7.0

... (truncated)

Commits

• e024a32 Prepare release 5.0.0
• 0ce8ac1 Drop support for specifying arbitrary type names in tags
• c8df563 Remove legacy backwards compatibility
• f96b7cc Ensure that tagged values are properly converted to the destination type
• 8f20a18 Prepare release 4.3.2
• 857192d Fix bug whe TypeConverter was being ignored on all platforms
• 145477a Remove serialization support from exceptions
• 113261c Add quick build task
• 837f61a Pin Cake version
• 667778b Merge pull request #313 from thoughtcroft/patch-1
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.