update component refs to 2026.03.0

[Whyborn]

This is a retry of #32, since it was having persistent openmpi problems. Closing that PR should clear the build cache of those builds, and force it to attempt to rebuild.

---

🚀 The latest prerelease access-am3/pr34-6 at ad20266 is here: #34 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr34-1 with commit a92ca5b

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr34-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/pr34-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/1.1/spack in the access-am3-pr34-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 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.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr34-2 with commit 31ea4a7

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr34-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/pr34-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-pr34-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.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr34-3 with commit d30dc3e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr34-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr34-3

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-pr34-3 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.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr34-4 with commit 342c493

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr34-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/pr34-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-pr34-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.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr34-5 with commit b01be37

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr34-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/pr34-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-pr34-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.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr34-6 with commit ad20266

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr34-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr34-6

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-pr34-6 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]

This brings in the latest changes from UM and JULES (this UM commit and this JULES commit). Tested with this config branch, gets bitwise identical results (bar the additional field added, which was the aim of the UM update).

[Whyborn]

@bschroeter if you do approve this, can you please merge it in while I'm away? This (and the corresponding configs PR is currently blocking some more of Jhan's work.

[bschroeter]

LGTM, merging.