Pull new spack-packages version which supports fetching UM commits

[Whyborn]

As title states, there was a bug in the UM build system that meant that it wasn't correctly checking out commits for the UM.

---

🚀 The latest prerelease access-am3/pr46-1 at 7eb28a8 is here: #46 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr46-1 with commit 7eb28a8

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.06.000 as a Release (when merged).
• pr46-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/pr46-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-pr46-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
• ACCESS-NRI/upstream-spack-packages version access/v1.1
• access-nri/access-spack-packages version 2026.05.005
• access-nri/spack-config version 2026.05.004

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]

@bschroeter The first of many which upgrades the spack packages with a bug fix. This does not come with any change to the source code, so I don't think it requires any model testing.