Merge pull request #54 from andrewlock/yaml-dotnet

Update YamlDotNet version

Author: andrewlock

README.md

@@ -49,7 +49,7 @@ PM> Install-Package NetEscapades.Configuration.Yaml
 When you install the package, it should be added to your _csproj_ file. Alternatively, you can add it directly by adding:
 
 ```xml
-<PackageReference Include="NetEscapades.Configuration.Yaml" Version="1.7.0" />
+<PackageReference Include="NetEscapades.Configuration.Yaml" Version="2.0.0" />
 ```
 
 To load a YAML file as part of your config, just load it as part of your normal `ConfigurationBuilder` setup in the `Program` class of your ASP.NET Core app. 
@@ -134,7 +134,7 @@ When you install the package, it should be added to your _csproj_. Alternatively
 
 
 ```xml
-<PackageReference Include="NetEscapades.Configuration.Remote" Version="1.5.0" />
+<PackageReference Include="NetEscapades.Configuration.Remote" Version="2.0.0" />
 ```
 
 To load a file from a remote configuration source as part of your config, just load it as part of your normal `ConfigurationBuilder` setup in the `Program` class of your ASP.NET Core app. 
@@ -191,7 +191,7 @@ PM> Install-Package NetEscapades.Configuration.Vault
 When you install the package, it should be added to your _csproj_. Alternatively, you can add it directly by adding:
 
 ```xml
-<PackageReference Include="NetEscapades.Configuration.Vault" Version="0.7.0" />
+<PackageReference Include="NetEscapades.Configuration.Vault" Version="0.8.0" />
 ```
 
 You can load secrets from a Vault instance as part of your configuration build. You can use any supported authentication method supported by [`VaultSharp`](https://github.com/rajanadar/VaultSharp), which is used under the hood, but an extension method exists for using `AppRole` specifically.

src/NetEscapades.Configuration.Remote/NetEscapades.Configuration.Remote.csproj

@@ -2,7 +2,7 @@
 
   <PropertyGroup>
     <Description>Remote configuration provider implementation to use with Microsoft.Extensions.Configuration for loading settings from a remote source</Description>
-    <VersionPrefix>1.5.0</VersionPrefix>
+    <VersionPrefix>2.0.0</VersionPrefix>
     <TargetFrameworks>net461;net472;netstandard2.0</TargetFrameworks>
     <AssemblyName>NetEscapades.Configuration.Remote</AssemblyName>
     <PackageId>NetEscapades.Configuration.Remote</PackageId>

src/NetEscapades.Configuration.Validation/NetEscapades.Configuration.Validation.csproj

@@ -2,7 +2,7 @@
 
   <PropertyGroup>
     <Description>A package to validate strongly typed configuration on app startup</Description>
-    <VersionPrefix>1.1.0</VersionPrefix>
+    <VersionPrefix>2.0.0</VersionPrefix>
     <TargetFrameworks>net461;net472;netstandard2.0;netstandard2.1</TargetFrameworks>
     <AssemblyName>NetEscapades.Configuration.Validation</AssemblyName>
     <PackageId>NetEscapades.Configuration.Validation</PackageId>

src/NetEscapades.Configuration.Yaml/NetEscapades.Configuration.Yaml.csproj

@@ -2,7 +2,7 @@
 
   <PropertyGroup>
     <Description>YAML configuration provider implementation to use with Microsoft.Extensions.Configuration.</Description>
-    <VersionPrefix>1.7.0</VersionPrefix>
+    <VersionPrefix>2.0.0</VersionPrefix>
     <TargetFrameworks>net461;net472;netstandard2.0</TargetFrameworks>
     <AssemblyName>NetEscapades.Configuration.Yaml</AssemblyName>
     <PackageId>NetEscapades.Configuration.Yaml</PackageId>
@@ -20,7 +20,7 @@
 
   <ItemGroup>
     <PackageReference Include="Microsoft.SourceLink.GitHub" Version="1.0.0-*" PrivateAssets="all" />
-    <PackageReference Include="YamlDotNet" Version="5.1.0" />
+    <PackageReference Include="YamlDotNet" Version="6.1.2" />
     <PackageReference Include="Microsoft.Extensions.Configuration" Version="2.0.0" />
     <PackageReference Include="Microsoft.Extensions.Configuration.FileExtensions" Version="2.0.0" />
   </ItemGroup>

src/NetEscapades.Configuration.Yaml/releasenotes.props

@@ -1,9 +1,10 @@
 <Project>
   <PropertyGroup>
-    <PackageReleaseNotes Condition="'$(VersionPrefix)' == '1.6.0'">
+    <PackageReleaseNotes Condition="'$(VersionPrefix)' == '2.0.0'">
       <![CDATA[
 Features:
-* Add support for Null values in YAML files (Thanks mdschweda: https://github.com/mdschweda)
+* Upgrade YamlDotNet to 6.1.2 - this is a breaking change in the dependency as the YamlDotNet.Signed and YamlDotNet packages were merged
+* Update supported frameworks - only supports .NET 461, .NET 472, and .NET Standard 2.0 (dropped support for 1.x)
 
 The following values are interpreted as 'null' during parsing (as per v1.1 of the spec http://yaml.org/type/null.html)