increased version to 1.7.0 (#411)

.config/dotnet-tools.json

@@ -9,7 +9,7 @@
       ]
     },
     "microsoft.coyote.cli": {
-      "version": "1.6.2",
+      "version": "1.7.0",
       "commands": [
         "coyote"
       ]

.github/workflows/test-coyote.yml

@@ -34,10 +34,6 @@ jobs:
         uses: actions/setup-dotnet@v1
         with:
           dotnet-version: '6.0.x'
-      - name: Setup .NET 5.0 SDK
-        uses: actions/setup-dotnet@v1
-        with:
-          dotnet-version: '5.0.x'
       - name: Setup .NET Core 3.1 SDK
         uses: actions/setup-dotnet@v1
         with:

Common/version.props

@@ -2,7 +2,7 @@
 <!-- This file may be overwritten by automation. Only values allowed here are VersionPrefix and VersionSuffix. -->
 <Project>
   <PropertyGroup>
-    <VersionPrefix>1.6.2</VersionPrefix>
+    <VersionPrefix>1.7.0</VersionPrefix>
     <VersionSuffix></VersionSuffix>
   </PropertyGroup>
 </Project>

History.md

@@ -1,4 +1,11 @@
 ## v1.7.0
+- Updated the default `random` exploration strategy with a `portfolio` testing mode that uses a
+  tuned set of different exploration strategies to increase coverage for different bug patterns. The
+  portfolio will be transparently enhanced over time as new exploration strategies become available
+  inside Coyote. The Portfolio can be set to fair or unfair using `Configuration.WithPortfolioMode`
+  or the `--portfolio-mode` command-line option. The portfolio mode can be disabled and explicitly
+  set to one of the available exploration strategies by setting a strategy-related option such as
+  `Configuration.WithRandomStrategy` or `-s <STRATEGY>`.
 - Refactored the NuGet packages, by moving `Microsoft.Coyote.Actors` to its own dedicated package,
   introducing a new `Microsoft.Coyote.Tool` package that contains the self-contained `coyote`
   command-line tool (for users that do not want to manage `coyote` via the `Microsoft.Coyote.CLI`
@@ -7,9 +14,10 @@
   pulls all non-tool packages.
 - Moved the actor `Event` type under the `Microsoft.Coyote.Actors` namespace.
 - Introduced a `Monitor.Event` type (nested in the `Microsoft.Coyote.Specifications.Monitor` class),
-  which must now be used for declaring specification monitor events.
-- Enhanced and streamlined the logging API, which is now available in the `Microsoft.Coyote.Logging`
-  namespace, instead of `Microsoft.Coyote.IO`.
+  which must now be used for declaring specification monitor events, instead of the original `Event`
+  type above.
+- Enhanced and streamlined the logging API and built-in loggers, which are now available in the
+  `Microsoft.Coyote.Logging` namespace, instead of `Microsoft.Coyote.IO`.
 - Removed support for the end-of-life `net5.0` target framework.
 
 ## v1.6.2

README.md

@@ -7,7 +7,7 @@
 ![Build and Test CI](https://github.com/microsoft/coyote/actions/workflows/test-coyote.yml/badge.svg?branch=main)
 ![CodeQL](https://github.com/microsoft/coyote/actions/workflows/codeql-analysis.yml/badge.svg?branch=main)
 
-Coyote is a library and tool for testing concurrent C# code and deterministically reproducing bugs.
+Coyote is a cross-platform library and tool for testing concurrent C# code and deterministically reproducing bugs.
 
 Using Coyote, you can easily test the *concurrency* and other *nondeterminism* in your C# code, by
 writing what we call a *concurrency unit test*. These look like your regular unit tests, but can
@@ -25,9 +25,9 @@ Coyote is made with :heart: by Microsoft Research.
 
 **New:** Check out our experimental [systematic testing library for
 C++](https://github.com/microsoft/cpp-systematic-testing) that is based on the same research and
-technology that powers Coyote.
+technology behind Coyote.
 
-## How it works?
+## How it works
 
 Consider the following simple test:
 ```csharp
@@ -81,10 +81,10 @@ fixing the issue significantly easier.
 ## Get started
 
 Getting started with Coyote is easy! First, follow this
-[guide](https://microsoft.github.io/coyote/#get-started/install/) to install `coyote` from
-[NuGet](https://www.nuget.org/packages/Microsoft.Coyote/). Then, check out
-[https://microsoft.github.io/coyote](https://microsoft.github.io/coyote/) for tutorials,
-documentation, how-tos, samples and more information about the project. Enjoy!
+[guide](https://microsoft.github.io/coyote/#get-started/install/) to install the `coyote`
+command-line tool from [NuGet](https://www.nuget.org/packages/Microsoft.Coyote/). You are now ready
+to check out the Coyote [website](https://microsoft.github.io/coyote/) for tutorials, documentation,
+how-tos, samples and more information about the project. Enjoy!
 
 If you are a Microsoft employee, please consider joining the internal-only [Friends of Coyote Teams
 channel](https://teams.microsoft.com/l/channel/19%3a1fe966b4fdc544bca648d89bf25c3c56%40thread.tacv2/General?groupId=7a6d8afc-c23d-4e5d-b9cb-9124118c0220&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47),
@@ -92,6 +92,8 @@ to be part of our community and learn from each other. Otherwise, please feel fr
 [discussion](https://github.com/microsoft/coyote/discussions) with us or open an
 [issue](https://github.com/microsoft/coyote/issues) on GitHub, thank you!
 
+Upgrading your `coyote` dependencies? Check the changelog [here](History.md).
+
 ## Contributing
 
 This project welcomes contributions and suggestions. Most contributions require you to agree to a

Scripts/CI/azure-nuget-sign-publish.yml

@@ -12,11 +12,6 @@ steps:
   inputs:
     useGlobalJson: true
 
-- task: UseDotNet@2
-  displayName: 'Install .NET 5.0 SDK'
-  inputs:
-    version: 5.0.x
-
 - task: UseDotNet@2
   displayName: 'Install .NET Core 3.1 SDK'
   inputs:

Tests/compare-rewriting-diff-logs.ps1

@@ -13,11 +13,11 @@ $targets = [ordered]@{
 }
 
 $expected_hashes = [ordered]@{
-    "rewriting" = "2BAA1A91DBD6BC406BE564C34DE3B7B03FE1A6251C91F781880D4688F99C13DF"
-    "rewriting-helpers" = "CC82EC742BDC1B678A89EC952257290AF8D935FA0DB1E8C5BB591D9AB3E18C77"
-    "testing" = "37A8AE3E92E2A07AA7DB57C3BC3D5B3FAAAE4E6D3D06673AB2BB353D28509880"
-    "actors" = "081E821326C12C11549C4091740D88360AE445619C413251F1B9A4B53053CE8B"
-    "actors-testing" = "E3611899F5BA62F32719BF59073C69E34CFECB3D9177CEE9FA6A3C3C5D4EE8C0"
+    "rewriting" = "81B3B708113A55B3E7D597EC93E8E2B1FA669CD146F84663BF340E03BFB9A93A"
+    "rewriting-helpers" = "9D6638DF52487AC25377D31BA8D0B1532C85F7BB5119751010D53ED02E247B17"
+    "testing" = "22C55B6369A5D82B2A1DE1B84FE8DD19514A53C086B2BBDC97DB16EEF8279C0F"
+    "actors" = "DED07E1858B24CFCA349A030A244F53174219463ACE92E2C62CA3C45CB94562C"
+    "actors-testing" = "79017E9E5C3D2FFDFABBC6316B04FBE83A1C8E2C434ECEC8E3686895C4BF82BE"
 }
 
 Write-Comment -prefix "." -text "Comparing the test rewriting diff logs" -color "yellow"