🚀Production Release (v13.6.1)

[CalvinWilkinson]

Prod-Release ToDo List

Complete the following items to perform a release.

Beta Give feedback

1. All of the issues in the assigned milestone are closed.
2. All issue tasks are checked/marked as complete.
3. The 🚀Production Release label has been added to this issue.
4. This issue is assigned to a project.
5. This issue is assigned to a milestone.
6. All of the unit tests have been executed locally and have passed. (Check out the appropriate branch before running tests).
7. The version has been updated. (All changes made directly on a 'prod-release' branch).
8. The release notes have been created. (All changes made directly on a 'prod-release' branch).
9. The pull request has been approved and merged into the main branch before performing the release. (Releases are performed on the main branch).
10. The production release has been completed. (The release is performed by running the 🚀Release workflow).

Post-Release ToDo List

Verify that release went smoothly.

Beta Give feedback

1. 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 JSON value in the deno.json file.

{
	"version": "v1.2.3",
    ...
}

---

Code of Conduct

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