Build with the latest CICE5 with the runtime params feature

[manodeep]

Deploying to test for bitwise repro for the OM2 configs

---

🚀 The latest prerelease access-om2/pr160-1 at 1836922 is here: #160 (comment) 🚀

[github-actions]

The model version in the spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

• !bump major for feature releases
• !bump minor for bugfixes

[github-actions]

🚀 Attempted to deploy access-om2 Prerelease pr160-1 with commit 1836922

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om2 Prerelease pr160-1 with commit 1836922

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.08.000 as a Release (when merged).
• pr160-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr160-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-om2-pr160-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.08.007
• access-nri/spack-config version 2026.08.001

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