Release: v5.1.0

[craddm]

✅ Checklist

Refer to the 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.
• 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

For patch releases only

• Confirm that the resource to which the patch applies can be successfully deployed

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
• Complete the Security evaluation checklist from the deployment documentation
• Add the new versions tag as an active build on Read The Docs (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
  2. ability to exfiltrate data from the system
  3. ability to transfer data between SREs
  4. ability to escalate privileges on the SRD.

Update documentation

• Update supported versions in SECURITY.md
• Update pen test results in VERSIONING.md

💻 Release information

• Version number: 5.1.0
• SHM ID: muppets
• T2 SRE ID: kermit
• T3 SRE ID: misspiggy

🌳 Deployment problems

• version number in version.py was still 5.0.1, not 5.1.0