Update JULES and UM versions

[Whyborn]

Updates on both model components for increased number of diagnostics, supporting Jiachen's urban work, and adding a namelist for CABLE.

---

🚀 The latest prerelease access-am3/pr32-5 at 4f0a5ff is here: #32 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr32-1 with commit 292080b

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in ./spack.yaml, will be deployed to Gadi as:

• 2026.03.000 as a Release (when merged).
• pr32-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr32-1

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-am3-pr32-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.004
• access-nri/spack-config version 2026.02.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr32-2 with commit 94508ed

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in spack.yaml, will be deployed to Gadi as:

• 2026.03.000 as a Release (when merged).
• pr32-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr32-2

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-am3-pr32-2 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 1.1
• spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
• access-nri/access-spack-packages version 2026.03.005
• access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

[Whyborn]

Confirmed that this bitwise reproduces the current release as expected.

[Whyborn]

I decided to update the UKCA ref to be the tag instead of the commit in this PR. It brings all the model component versions (which we provide a ref for) up to 2026.03.0, and logically updates the AM3 version.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr32-3 with commit 4f0a5ff

🖥️ Gadi Deployment ❌

[Whyborn]

!redeploy

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr32-4 with commit 4f0a5ff

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in spack.yaml, will be deployed to Gadi as:

• 2026.03.000 as a Release (when merged).
• pr32-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr32-4

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-am3-pr32-4 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 1.1
• spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
• access-nri/access-spack-packages version 2026.03.005
• access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

[Whyborn]

!redeploy

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr32-5 with commit 4f0a5ff

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in spack.yaml, will be deployed to Gadi as:

• 2026.03.000 as a Release (when merged).
• pr32-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr32-5

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-am3-pr32-5 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 1.1
• spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
• access-nri/access-spack-packages version 2026.03.005
• access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

[Whyborn]

There's a persistent issue with openmpi- trying to rebuild. Closing the PR, to remove the builds from the cache and hopefully force it to rebuild properly.