Release 4.9.1

• Address all coding and style violations detected during a Release build (send a regular pull request which must be merged before continuing)
• ensure completeness of draft release notes, including non-owner contributors, if any (move release notes forward from any pre-releases to the current release)
• run tools\prepare_release.cmd x.y.z to:
  • change “vNext” names to appropriate x.y.z version for the next GitHub Release, milestone, and release checklist (this issue)
  • create a new draft GitHub Release, milestone, and release checklist
  • create release/x.y.z branch on upstream, branching from develop
  • submit a pull request to merge the release/x.y.z branch to master
• merge the pull request, which may be done by the PR creator, unlike a regular pull request
• tag master with the new version number and push to upstream. This will cause the build server to
  • push the nupkgs to nuget.org and
  • attach all nupkgs from the tagged build to the GitHub Release.
• wait for NuGet package validation
• de-list pre-release NuGet packages if present
• publish the GitHub release
• tweet, mentioning contributors, and post link as comment here for easy retweeting 😉
• post tweet in Gitter
• post a link to the GitHub Release in each issue in this milestone, with thanks to contributors
• close this issue
• close the milestone for this release

[thomaslevesque]

Faked method calls from within concurrent threads don’t get recognized by FakeItEasy all of the time

I’d change the wording of this to something like “Call assertions sometimes fail for concurrent calls”

[blairconrad]

https://twitter.com/fakeiteasyfx/status/1045641213372706816

This change has been released as part of FakeItEasy 4.9.1.