Merge branch 'develop' into add-command-reference

.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
 
@@ -34,26 +34,27 @@ Refer to the [Deployment](https://data-safe-haven.readthedocs.io/en/latest/deplo
 ### 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