docs: update changelog

Author: egil

CHANGELOG.md

@@ -6,6 +6,23 @@ All notable changes to **bUnit** will be documented in this file. The project ad
 
 ## [Unreleased]
 
+This release includes support for .NET 6, with support for all new features in Blazor with that release. There are also a number of additions and fixes, all listed below.
+
+Big shout out to **bUnit's sponsors** who helped make this release happen.
+
+**The higher tier sponsors are:**
+
+- [Progress Telerik](https://github.com/Progress-Telerik)
+- [Syncfusion](https://github.com/syncfusion)
+
+**Other sponsors are:**
+
+- [Hassan Rezk Habib (@Garderoben)](https://github.com/hassanhabib)
+- [Jonny Larsson (@Garderoben)](https://github.com/Garderoben)
+- [Domn Werner (@domn1995)](https://github.com/domn1995)
+- [Mladen Macanović (@stsrki)](https://github.com/stsrki)
+- [@ChristopheDEBOVE](https://github.com/ChristopheDEBOVE)
+
 ### Added
 
 List of added functionality in this release.
@@ -31,6 +48,8 @@ List of added functionality in this release.
 
 - Added `History` capture in the `FakeNavigationManager`. By [@egil](https://github.com/egil).
 
+- Added new bUnit component mocking library, available via NuGet as `bunit.web.mock`. It is currently in preview and the features/APIs of it will change!
+
 ### Fixed
 
 - The `Click` and `DoubleClick` extension methods now set the `MouseEventArgs.Detail` property to `1` and `2` respectively by default, unless the user specifies something else. This makes the methods more correctly emulate how Blazor reports single or double clicks on an element in the browser. Thanks to [@David-Moreira](https://github.com/David-Moreira) for the help troubleshooting this issue. By [@egil](https://github.com/egil).
@@ -39,6 +58,8 @@ List of added functionality in this release.
 
 - Fixes handling of disposed event handlers of bubbling events. See issue [#518](https://github.com/bUnit-dev/bUnit/issues/518) for details. Thanks to [@David-Moreira](https://github.com/David-Moreira) for helping debug this issue.
 
+- Async event trigger methods are not public. In most circumstances you do not need to use them, but if you have a scenario where you want to check that something has not happened after an event handler was triggered, then you can use the async methods and await them to know when they are completed. See [#552](https://github.com/bUnit-dev/bUnit/discussions/552) for details. By [@egil](https://github.com/egil).
+
 ## [1.2.49] - 2021-08-09
 
 ### Added