Update to upstream oasis3-mct v5.2

[manodeep]

Creating the deployment for merging in the update to oasis3-mct v5.2 - will need to confirm bitwise repro before merging.

---

🚀 The latest prerelease access-esm1p6/pr177-17 at 5dfc6e0 is here: #177 (comment) 🚀

[manodeep]

@blimlim I have requested your review but I want to update (at least) the PI config

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr177-17 with commit 5dfc6e0

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.12.001 as a Release (when merged).
• pr177-17 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr177-17

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-esm1p6-pr177-17 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.11.001
• access-nri/spack-config version 2025.08.000

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

[blimlim]

Thanks @manodeep, looks good to me

[manodeep]

@blimlim and I had a Zulip checkin and it should be fine to merge this in and get a "released" model. The config updates can then use the released exes to check for bitwise repro

[dougiesquire]

@blimlim and I had a Zulip checkin and it should be fine to merge this in and get a "released" model. The config updates can then use the released exes to check for bitwise repro

You can of course always check repro with the prerelease deployments before merging to avoid any nasty surprises

[manodeep]

Thanks @dougiesquire! I have previously tested that bitwise repro is not broken with upstream oasis3-mct here. But our code has changed since then ...