Update changelog and bump version to 1.0.0-alpha.22

CHANGELOG.md

@@ -9,6 +9,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### New features
 
+### Changes to existing features
+
+### Bugs fixed in this release
+
+### Known problems introduced by this release
+
+## [1.0.0-alpha.22](https://github.com/Buildvana/Buildvana.Sdk/releases/tag/1.0.0-alpha.22) (2022-09-22)
+
+### New features
+
 - Quite a few more properties are exported to the external `NuSpecFile`. The complete list can be seen [in the source code](https://github.com/Buildvana/Buildvana.Sdk/blob/main/src/Buildvana.Sdk/Modules/NuGetPack/NuspecFile.targets). A notable addition is `configuration`, the only default "nuspec property" missing in Buildvana SDK so far.
 - Files used for the generation of a NuGet package are now shown in Visual Studio's Solution Explorer tree view, under a "virtual" folder named "- Package". This includes: the license file, the third-party notice file, the Readme file, the package icon, and the `NuspecFile` if specified either explicitly or implicitly (i.e. by having a `{ProjectName}.nuspec` file in the project folder).
 - When using public API analyzers, [TFM-specific public API files](https://github.com/dotnet/roslyn-analyzers/blob/main/src/PublicApiAnalyzers/PublicApiAnalyzers.Help.md#conditional-api-differences) are added to the project automatically.
@@ -22,8 +32,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - When using an external `.nuspec` file, the `$configuration$` tag did not work in previous versions of Buildvana SDK. This has been fixed.
 - When using an external `.nuspec` file, the `$repositoryType$` tag did not work in previous versions of Buildvana SDK. This has been fixed.
 
-### Known problems introduced by this release
-
 ## [1.0.0-alpha.21](https://github.com/Buildvana/Buildvana.Sdk/releases/tag/1.0.0-alpha.21) (2022-09-20)
 
 ### New features

VERSION

@@ -1 +1 @@
-1.0.0-alpha.21
+1.0.0-alpha.22