Release v5.2.0

.github/ISSUE_TEMPLATE/deployment_bug_report.md

@@ -29,7 +29,6 @@ Before reporting a problem please check the following. Replace the empty checkbo
 <summary>List of packages</summary>
 
 <!--
-Powershell: Run `deployment/CheckRequirements.ps1` and paste the output below
 Python: Run `hatch run pip freeze` and paste the output below
 -->
 

.github/ISSUE_TEMPLATE/release_checklist.md

@@ -14,9 +14,9 @@ Before reporting a problem please check the following. Replace the empty checkbo
 
 Refer to the [Deployment](https://data-safe-haven.readthedocs.io/en/latest/deployment) section of our documentation when completing these steps.
 
-- [ ] Consult the `data-safe-haven/VERSIONING.md` guide and determine the version number of the new release. Record it in the title of this issue.
+- [ ] Consult the `data-safe-haven/VERSIONING.md` guide and determine the version number of the new release. Record it in the title of this issue
 - [ ] Create a release branch called e.g. `release-v0.0.1`
-- [ ] Draft a changelog for the release similar to our previous releases, see https://github.com/alan-turing-institute/data-safe-haven/releases
+- [ ] Draft a changelog for the release similar to our [previous releases](https://github.com/alan-turing-institute/data-safe-haven/releases)
 
 ### For patch releases only
 
@@ -25,35 +25,34 @@ Refer to the [Deployment](https://data-safe-haven.readthedocs.io/en/latest/deplo
 ### For minor releases and above
 
 - [ ] Deploy an SHM from this branch and save a transcript of the deployment logs
-- Using the new image, deploy a tier 2 and a tier 3 SRE
-    - [ ] Save the transcript of your tier 2 SRE deployment
-    - [ ] Save the transcript of your tier 3 SRE deployment
+- [ ] Deploy a tier 2 SRE from this branch and save the transcript of the deployment logs
+- [ ] Deploy a tier 3 SRE from this branch and save the transcript of the deployment logs
 - [ ] Complete the [Security evaluation checklist](https://data-safe-haven.readthedocs.io/en/latest/deployment/security_checklist.html) from the deployment documentation
-- [ ] Add the new versions tag as an active build on [Read The Docs](https://readthedocs.org) (You can add as a hidden build, before release, to preview)
 
 ### For major releases only
 
 - [ ] Confirm that a third party has carried out a full penetration test evaluating:
-  1. external attack surface
-  1. ability to exfiltrate data from the system
-  1. ability to transfer data between SREs
-  1. ability to escalate privileges on the SRD.
+    1. external attack surface
+    1. ability to exfiltrate data from the system
+    1. ability to transfer data between SREs
+    1. ability to escalate privileges on the SRD.
 
 ### Update documentation
 
 - [ ] Update supported versions in `SECURITY.md`
 - [ ] Update pen test results in `VERSIONING.md`
 
-## :computer: Release information
+### Making the release
 
-- **Version number:** _
-- **SHM ID:** _
-- **T2 SRE ID:** _
-- **T3 SRE ID:** _
+- [ ] Merge release branch into `latest`
+- [ ] Create a tag of the form `v0.0.1` pointing to the most recent commit on `latest` (the merge that you just made)
+- [ ] Publish your draft GitHub release using this tag
+- [ ] Ensure docs for the latest version are built and deployed on ReadTheDocs
+- [ ] Push a build to PyPI
+- [ ] Announce release on communications channels
 
 ## :deciduous_tree: Deployment problems
 
 <!--
 Keep a record in this issue of problems and fixes implemented during the release process. Be sure to update the changelog if any new commits are added to the release branch.
 -->
-

.github/workflows/lint_code.yaml

@@ -108,7 +108,7 @@ jobs:
           done
           rm expanded.tmp
       - name: Lint YAML
-        uses: karancode/yamllint-github-action@v2.1.1
+        uses: karancode/yamllint-github-action@v3.0.0
         with:
           yamllint_strict: true
           yamllint_comment: false

.hatch/requirements-docs.txt

@@ -91,7 +91,7 @@ typing-extensions==4.12.2
     # via pydata-sphinx-theme
 urllib3==2.2.3
     # via requests
-wheel==0.45.0
+wheel==0.45.1
     # via sphinx-togglebutton
 
 # The following packages are considered to be unsafe in a requirements file: