Release notes for 11.0.0-alpha1

README.md

@@ -83,6 +83,8 @@ What follows is the Table of Contents for this README, which also serves as the
 - [About test parallelism](#about-test-parallelism)
   - [What does 'expected to have type TestCode' mean?](#what-does-expected-to-have-type-testcode-mean)
   - [My tests are hanging and I can't see why](#my-tests-are-hanging-and-i-cant-see-why)
+- [Migration notes](#migration-notes)
+  - [11.0.0](#1100)
 
 <!-- tocstop -->
 
@@ -1369,4 +1371,6 @@ This might be due to how terminals/the locking thereof work: try running your te
 
 ## Migration notes
 
-- 11.0.0: Any usages of the `replay` (a.k.a `stdGen` with `etestProperty*` functions) config with FsCheck tests will need to be updated to use `uint64` by appending `UL` to the literals, e.g. from `(1865288075, 296281834)` to `(1865288075UL, 296281834UL)`.
+### 11.0.0
+- Any usages of the `replay` (a.k.a `stdGen` with `etestProperty*` functions) config with FsCheck tests will need to be updated to use `uint64` by appending `UL` to the literals, e.g. from `(1865288075, 296281834)` to `(1865288075UL, 296281834UL)`.
+- FsCheck 2 is no longer supported, so we're switching Expecto.FsCheck to use FsCheck 3 by default, even though FsCheck 3 is still in release candidate state. If you still want FsCheck2, we will continue to release FsCheck2 support for the time being using a version suffix, e.g. [11.0.0-fscheck2](https://www.nuget.org/packages/Expecto.FsCheck/11.0.0-alpha1-fscheck2)  

RELEASE_NOTES.md

@@ -1,5 +1,6 @@
-### 11.0.0 - 2024-08-14
+### 11.0.0-alpha1 - 2024-08-14
 * Fix testTheory issue where null and empty string produce duplicate test names (#494), thanks @Numpsy
+* Breaking Change: FsCheck 3 is now the default for Expecto.FsCheck, since FsCheck 2 is no longer supported. FsCheck 2 support is still available under the `-fscheck2` version suffix (i.e. install Expecto.FsCheck with version [11.0.0-alpha1-fscheck2](https://www.nuget.org/packages/Expecto.FsCheck/11.0.0-alpha1-fscheck2))
 * Breaking Change: move `FsCheckConfig.replay` from `int` to `uint64` (#501), thanks @rynoV
   * Fixes issue where many FsCheck3 runs could not be replayed since the random seed is too large.
   * Existing FsCheck 2 users should be able to use the same seeds values, but converted to `uint64`.