Update package version and release notes for v2.0.1

CHANGELOG.md

@@ -5,7 +5,11 @@ All notable changes to the [Unity3D NuGet package](https://www.nuget.org/package
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## Upcoming
+## 2.0.1 - 2022-06-01
+
+### Changed
+
+- All documentation and package details now reference the Rabadash8820 GitHub repository (transferred from DerploidEntertainment)
 
 ## 2.0.0 - 2022-06-01
 

README.md

@@ -70,7 +70,7 @@ Add a `UnityVersion` property to your .csproj, so it looks like the following:
         <UnityVersion>2022.1.1f1</UnityVersion>
     </PropertyGroup>
     <ItemGroup>
-        <PackageReference Include="Unity3D" Version="2.0.0" />
+        <PackageReference Include="Unity3D" Version="2.0.1" />
     </ItemGroup>
     <!-- Other properties/items -->
 </Project>

nupkg/Unity3D.nuspec

@@ -2,7 +2,7 @@
 <package xmlns="http://schemas.microsoft.com/packaging/2013/01/nuspec.xsd">
   <metadata minClientVersion="2.5">
     <id>Unity3D</id>
-    <version>2.0.0</version>
+    <version>2.0.1</version>
     <title>Unity</title>
     <authors>Unity Technologies</authors>
     <icon>icon.png</icon>
@@ -11,23 +11,7 @@
     <projectUrl>https://github.com/Rabadash8820/UnityAssemblies</projectUrl>
     <description>Simple, forward-compatible references to ANY Unity assembly on ANY platform.</description>
     <releaseNotes>
-- Unity version can now be parsed automatically from the ProjectVersion.txt file in a Unity project, if not set explicitly.
-- Added many new short-hand properties, with more consistent naming (relative paths end in "Dir" or "Assembly", absolute paths end in "Path")
-- If neither UnityVersion nor UnityProjectPath are explicitly set, then UnityVersion is set to a constant string to explain the issue
-- UnityVersion or UnityProjectPath must be set in a Directory.Build.props, not the project file.
-- Added UnityVersionMajor, UnityVersionMinor, UnityVersionPatch, and UnityVersionAsNumber props for manipulation of Unity versions as numbers
-- Updated usage notes in all Readme documents
-- Internal: added test projects for Tech Stream Unity releases up through 2022.1
-- Added a changelog with release notes for all versions thus far, based on Keep a Changelog
-- Added Documentation on using the numeric Unity version properties in MSBuild files
-- Added Support documentation to main README
-- Added a changelog to the repo based on Keep a Changelog
-- Updated ASCII art in package readme.txt to use new Unity logo
-- Updated package icon to use new Unity logo
-- BREAKING CHANGES:
-  - Renamed "OSInstallRoot" property to "OSInstallRootPath" and "UnityInstallRoot" to "UnityInstallRootPath", to be consistent with other prop names
-  - Reference Include paths no longer need to start with $(UnityInstallRoot)/$(UnityVersion). Most paths will now use a single short-hand property
-  - Assembly short-hand properties are now conditionally defined based on UnityVersion
+- All documentation and package details now reference the Rabadash8820 GitHub repository (transferred from DerploidEntertainment)
     </releaseNotes>
     <copyright>Copyright ©2019-2022 Daniel Vicarel</copyright>
     <tags>Unity Unity3D UnityEngine UnityEditor</tags>

nupkg/readme.txt

@@ -36,7 +36,7 @@ Then, make sure your .csproj file looks something like this:
             <TargetFramework>netstandard2.1</TargetFramework>
         </PropertyGroup>
         <ItemGroup>
-            <PackageReference Include="Unity3D" Version="2.0.0" />
+            <PackageReference Include="Unity3D" Version="2.0.1" />
         </ItemGroup>
         <!-- Other properties/items -->
     </Project>