🚀Production Release (v1.0.0)

[CalvinWilkinson]

Pre-Release ToDo List

• All issues in the assigned milestone are closed and all issue tasks are complete.
• Add 🚀Production Release label to this pull request.
• The pull request is assigned to a project.
• 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.
• Release notes created.
• Release to production completed. (The release is performed by running the 🚀Release workflow).

Post-Release ToDo List

• The GitHub release has been created and is correct.

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 production release version.
The <AssemblyVersion/> XML tag can only hold production values. Preview values are not allowed.

<!--Production Release Example-->
<Version>1.2.3</Version>
<FileVersion>1.2.3</FileVersion>
<AssemblyVersion>1.2.3</AssemblyVersion>

---

Code of Conduct

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