Add Release notes and Migration notes.

Author: StevenTCramer

Documentation/Migrations/Migration4-5.md

@@ -0,0 +1,20 @@
+---
+uid: BlazorState:Migration4-5.md
+title: Migrate From 4.X to 5.X
+---
+
+# Migration
+
+## From 4.X to 5.X
+
+The biggest requirement will be to migrate to dotnet 6. See [Migrate from ASP.NET Core 5.0 to 6.0](https://docs.microsoft.com/en-us/aspnet/core/migration/50-to-60?view=aspnetcore-6.0&tabs=visual-studio)
+
+After completing that dotnet 6 migration the blazor-state specific changes are as follows:
+
+### Remove the script tag in your index.html or _Host.cshtml files
+
+Delete:
+
+```html
+<script src="_content/BlazorState.js/blazorstate.js"></script>
+```

Documentation/ReleaseNotes/Release5.0.0.md

@@ -0,0 +1,23 @@
+---
+uid: BlazorState:Release.5.0.0.md
+title: Release 5.0.0
+---
+
+## Release 5.0.0
+
+### Breaking Changes
+* Blazor-State has moved to net6.0
+* <script src="_content/Blazor-State/blazorstate.js"></script> is no longer needed and should be removed.
+* Updated Mediator to 10.0.1 https://jimmybogard.com/mediatr-10-0-released/
+* Requires Browsers that support module import.  [CanIUse](https://caniuse.com/?search=module)
+
+See [Migrations](xref:BlazorState:Migration4-5.md) for how to migrate existing projects from 4.0 to 5.0.
+
+### Other Changes
+* Include debug symbols in main nuget package vs separate.
+* Switch from Shouldly to FluentValidations
+* Move to `Directory.Packagaes.props`
+* Move to esproj and remove webpack.
+* In dotnet 6 there are new capabilities to initialize JS modules. 
+* Move to file based namespaces;
+* Run dotnet format on all.