🚀Preview Release (v1.0.0-preview.2)

[CalvinWilkinson]

Pre-Release ToDo List

• All issues in the assigned milestone are closed and all issue tasks are complete.
• Add 🚀Preview Release label to this pull request.
• The pull request is assigned to a project.
• The pull request is assigned to a milestone.
• All unit tests have been executed locally and have passed. (Check out the appropriate release branch before running tests).
• The version in the csharp project file updated.
• Auto-generated release notes have been reviewed and updated if necessary.
• Manual QA Testing completed (if applicable).
• Release to preview completed. (The release is performed by running the 🚀Release workflow).

Post-Release ToDo List

• The GitHub release has been created and is correct.
• The NuGet package has been successfully deployed to nuget.org (if applicable).
• Announcement of release on Twitter verified. (if applicable).
• An announcement has been pushed to the Discord channel. (if applicable)
• Documentation website released with updated or added tutorials. (if applicable)
• The documentation website has been released with updated API changes. (if applicable)

Additional Information:

Unit Tests

Reasons for local unit test execution:

• Unit tests might pass locally but not in the CI environment during the status check process or vice-versa.
• Tests might pass on the developer's machine but not necessarily on the code reviewer's machine.

---

Version Updating

The version can be updated by setting the values of the <Version/> and <FileVersion/> XML tags in the project file.
The <Version/> and <FileVersion/> values can hold the preview release version.
The <AssemblyVersion/> XML tag can only hold production values. Preview values are not allowed.

<!--Preview Release Example-->
<Version>1.2.3-preview.4</Version>
<FileVersion>1.2.3-preview.4</FileVersion>
<AssemblyVersion>1.2.3</AssemblyVersion>

---

Code of Conduct

• I agree to follow this project's Code of Conduct