diff --git a/Makefile b/Makefile
index e94b133155..b064c4b077 100644
--- a/Makefile
+++ b/Makefile
@@ -391,7 +391,7 @@ STERN_VERSION = v2.6.1
 CHART_TESTING_VERSION = v3.11.0
 K3D_IMAGE = docker.io/rancher/k3s:v1.30.1-k3s1
 TESTS = [nginx,api,features-kubernetes,bulk-deployment,features-kubernetes-2,features-variables,active-standby-kubernetes,tasks,drush,python,gitlab,github,bitbucket,services,workflows]
-CHARTS_TREEISH = lagoon-220
+CHARTS_TREEISH = main
 TASK_IMAGES = task-activestandby
 
 # the name of the docker network to create
diff --git a/docs/releases/2.20.0.md b/docs/releases/2.20.0.md
index 3f42115713..d2d6a01995 100644
--- a/docs/releases/2.20.0.md
+++ b/docs/releases/2.20.0.md
@@ -1,7 +1,10 @@
 #### Release Links
-
-!!! Info
-    This version has not been released yet
+* lagoon [v2.20.0](https://github.com/uselagoon/lagoon/releases/tag/v2.20.0)
+* lagoon-ui [core-v2.20.0](https://github.com/uselagoon/lagoon-ui/releases/tag/core-v2.20.0)
+* lagoon-build-deploy [core-v2.20.0](https://github.com/uselagoon/build-deploy-tool/releases/tag/core-v2.20.0)
+* lagoon-core chart [1.46.0](https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-core-1.46.0)
+* lagoon-remote chart [0.92.0](https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-remote-0.92.0)
+* lagoon-test chart: [0.58.0](https://github.com/uselagoon/lagoon-charts/releases/tag/lagoon-test-0.58.0)
 
 ## Upgrades
 
@@ -13,8 +16,11 @@ This release contains changes that you may need to be aware of. Read carefully b
 
 ## Deprecations
 
+### Kubernetes minimum supported version is now 1.25, tested up to 1.30
+* The minimum supported version of Kubernetes is now 1.25, owing to deprecations in some core [API functions](https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25), and the availability of upstream charts. The v2.20.0 release will not install into an earlier version of Kubernetes, so any Kubernetes upgrades will need to be performed prior to the Lagoon update.
+
 ### Deleted Backups
-* When a backup is deleted via the webhook, it will now actually removed from the API rather than being flagged as deleted. The `Backup` type field `deleted` is deprecated, and will be removed in a future release. Additionally, `includeDeleted` if requested when querying backups will not change the result as there will be no deleted backups to include.
+* When a backup is deleted via the webhook, it will now actually be removed from the API rather than being flagged as deleted. The `Backup` type field `deleted` is deprecated, and will be removed in a future release. Additionally, `includeDeleted` if requested when querying backups will not change the result as there will be no deleted backups to include.
 
 ### API Harbor support
 * In [v2.17.0](https://docs.lagoon.sh/releases/2.17.0/#api-harbor-support) we announced that Harbor support in the API was deprecated. This release of Lagoon removes all support for Harbor from the API. See upgrade notes above.
@@ -23,4 +29,4 @@ This release contains changes that you may need to be aware of. Read carefully b
 * This release removes all `DeleteAllX` and `RemoveAllX` from the API. These were only ever meant for local development and are no longer relevant.
 
 ### Error handling on deployment triggers
-* In the past, if triggering a deployment using any of the `DeployEnvironmentX` mutations and an error was encountered, the API would not return an actual error, just a string that contained the error. This was changed in this release to actually return an error now. As this is a change in behaviour, it may impact any users that may have previously been capturing the string error text and parsing it to check for errors.
\ No newline at end of file
+* In the past, if triggering a deployment using any of the `DeployEnvironmentX` mutations and an error was encountered, the API would not return an actual error, just a string that contained the error. This was changed in this release to actually return an error now. As this is a change in behaviour, it may impact any users that may have previously been capturing the string error text and parsing it to check for errors.