Test MOM6 2026.01 release candidate

[dougiesquire]

This PR is to create a prerelease for testing the HEAD of the new MOM6 2026.01 release branch

---

🚀 The latest prerelease access-om3/pr177-2 at 5d0d9f6 is here: #177 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr177-1 with commit 218ea25

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.001 as a Release (when merged).
• pr177-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr177-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-om3-pr177-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.12.000
• 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.

[dougiesquire]

!update-configs

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr177-2 with commit 5d0d9f6

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.001 as a Release (when merged).
• pr177-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr177-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/0.22/spack in the access-om3-pr177-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 0.22
• access-nri/spack-packages version 2025.12.000
• 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.

[dougiesquire]

!update-configs

[dougiesquire]

!update-configs

[github-actions]

🔧 Opening Model Configuration PRs in ACCESS-NRI/access-om3-configs

Configurations Requested

Configurations requested from profile default:

• dev-MC_100km_jra_ryf

• dev-MC_100km_jra_ryf+wombatlite

• dev-MC_25km_jra_ryf

Pull Requests Opened

The following PRs were opened:

• Auto update dev-MC_100km_jra_ryf to use access-om3/pr177-2 access-om3-configs#1043

• Auto update dev-MC_100km_jra_ryf+wombatlite to use access-om3/pr177-2 access-om3-configs#1042

• Auto update dev-MC_25km_jra_ryf to use access-om3/pr177-2 access-om3-configs#1041

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/20941948510

[dougiesquire]

Purpose served

[chrisb13]

@dougiesquire. Thanks for pointing out the example (from here).

Why did you type the command twice:

• Test MOM6 2026.01 release candidate #177 (comment)
• Test MOM6 2026.01 release candidate #177 (comment)

So does this basically run a repro test on a config?

On these configs

• dev-MC_100km_jra_ryf
• dev-MC_100km_jra_ryf+wombatlite
• dev-MC_25km_jra_ryf

So this is handy for testing a build but doesn't do the update bit that we've been discussing?

[dougiesquire]

Why did you type the command twice:

I had to fix a typo in the workflow on main

[dougiesquire]

So does this basically run a repro test on a config?\n\nOn these configs\n\ndev-MC_100km_jra_ryf\ndev-MC_100km_jra_ryf+wombatlite\ndev-MC_25km_jra_ryf\nSo this is handy for testing a build but doesn't do the update bit that we've been discussing?

Correct.

[chrisb13]

Correct.

Is the process described/written down somewhere?

[dougiesquire]

Is the process described/written down somewhere?

There's this in the ACCESS-NRI/build-cd repo, but that's not a lot of detail. It's a very new feature. I think this PR might be the first to use it on a real model and configs.

It's described pretty well in @CodeGat's PR adding the functionality to this repo (where you were pinged as a reviewer).