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

[CalvinWilkinson]

Pre-Release ToDo List

Beta Give feedback

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

Post-Release ToDo List

Beta Give feedback

1. The GitHub release has been created and is correct.
2. The NuGet package has been successfully deployed to nuget.org (if applicable).
3. Announcement of release on Twitter verified. (if applicable).
4. An announcement has been pushed to the Discord channel. (if applicable)
5. Documentation website released with updated or added tutorials. (if applicable)
6. 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