Release 2026.02.000 v2 by anton-seaice · Pull Request #135 · ACCESS-NRI/ACCESS-OM2

anton-seaice · 2026-02-17T04:02:33Z

A redo of #133, now with the multiple CICE exes handled by CMake, rather than Spack. We also moved to Spack v1.1 in the meantime, so easiest to create a new PR rather than rebase #133.

Next release of ACCESS-OM2:

Update access-generic-tracers
Update cice5 (and parallelio) closes CICE5 with updated ParallelIO #129 and CICE5 CMake Build #126

🚀 The latest prerelease access-om2/pr135-9 at 8fc280c is here: #135 (comment) 🚀

🚀 The latest prerelease access-om2/pr135-10 at cefcacd is here: #135 (comment) 🚀

github-actions · 2026-02-17T04:08:28Z

🚀 Attempted to deploy access-om2 Prerelease pr135-1 with commit 75f1fd1

🖥️ `Gadi` Deployment ❌

github-actions · 2026-02-17T22:25:17Z

🚀 Attempted to deploy access-om2 Prerelease pr135-2 with commit ee2128c

🖥️ `Gadi` Deployment ❌

github-actions · 2026-02-17T23:29:25Z

🚀 Attempted to deploy access-om2 Prerelease pr135-3 with commit 52d9a7a

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.000 as a Release (when merged).
pr135-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr135-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-om2-pr135-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 39aeb9dbcc13b6a53e40c77b672c397e1f4c93ec
access-nri/access-spack-packages version 1cc3b883e8825d1fd3794d34b653f22bbbdd9c0d
access-nri/spack-config version 2026.02.001

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.

anton-seaice · 2026-02-17T23:33:39Z

!update-configs

github-actions · 2026-02-17T23:34:33Z

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

Configurations Requested

Configurations requested from profile default:

dev-01deg_jra55_ryf
dev-025deg_jra55_ryf
dev-1deg_jra55_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

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

anton-seaice · 2026-02-17T23:37:52Z

Seems to make exes ok:

[as2285@gadi-login-07 as2285]$ module use /g/data/vk83/prerelease/modules
[as2285@gadi-login-07 as2285]$ module load access-om2/pr135-3
Loading access-om2/pr135-3
  Loading requirement: access-om2/dependencies/pr135-3/oasis3-mct/2025.03.001-mfv6lca access-om2/dependencies/pr135-3/libaccessom2/2025.05.001-ypcr7e3
    access-om2/dependencies/pr135-3/cice5/2026.01.000-emthaid access-om2/dependencies/pr135-3/mom5/2025.08.000-4pdys3g
[as2285@gadi-login-07 as2285]$ ci
cice_auscom_1440x1080_30x27.exe  cice_auscom_3600x2700_40x30.exe  cice_auscom_360x300_15x300.exe

github-actions · 2026-02-17T23:38:31Z

🚀 Attempted to deploy access-om2 Prerelease pr135-4 with commit d84a484

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.000 as a Release (when merged).
pr135-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr135-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-om2-pr135-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 39aeb9dbcc13b6a53e40c77b672c397e1f4c93ec
access-nri/access-spack-packages version 1cc3b883e8825d1fd3794d34b653f22bbbdd9c0d
access-nri/spack-config version 2026.02.001

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.

anton-seaice · 2026-02-18T00:13:18Z

Auto update dev-01deg_jra55_ryf to use access-om2/pr135-3 access-om2-configs#256

Auto update dev-025deg_jra55_ryf to use access-om2/pr135-3 access-om2-configs#257

Auto update dev-1deg_jra55_ryf to use access-om2/pr135-3 access-om2-configs#255

These three all maintain historical repro

github-actions · 2026-02-18T05:45:37Z

🚀 Attempted to deploy access-om2 Prerelease pr135-5 with commit 8f5f1ac

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.000 as a Release (when merged).
pr135-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr135-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-om2-pr135-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 1cc3b883e8825d1fd3794d34b653f22bbbdd9c0d
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.

anton-seaice · 2026-02-18T22:02:41Z

This change release ACCESS-OM2 with new CICE5 and WOMBATlite versions

@dougiesquire

Closes #129

github-actions · 2026-02-18T22:04:48Z

🚀 Attempted to deploy access-om2 Prerelease pr135-6 with commit 8fc280c

🖥️ `Gadi` Deployment ❌

anton-seaice · 2026-02-18T22:05:26Z

!redeploy

github-actions · 2026-02-18T22:10:22Z

🚀 Attempted to deploy access-om2 Prerelease pr135-8 with commit 8fc280c

🖥️ `Gadi` Deployment ❌

anton-seaice · 2026-02-18T22:15:32Z

!redeploy

github-actions · 2026-02-18T22:15:40Z

🚀 Attempted to deploy access-om2 Prerelease pr135-6 with commit 8fc280c

🖥️ `Gadi` Deployment ❌

github-actions · 2026-02-18T22:26:58Z

🚀 Attempted to deploy access-om2 Prerelease pr135-9 with commit 8fc280c

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr135-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr135-9

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-pr135-9 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.02.003
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.

anton-seaice · 2026-02-18T22:37:10Z

I didn't realise that pushing the commit and setting ready for review triggered TWO builds, which then conflicted, and I kept causing conflicts by redeploying too fast

dougiesquire

LGTM

spack.yaml

@dougiesquire

Apply suggestion from @dougiesquire Co-authored-by: Dougie Squire <dougiesquire@gmail.com>

anton-seaice · 2026-02-18T22:55:00Z

Could you approve again please @dougiesquire

github-actions · 2026-02-18T22:57:59Z

🚀 Attempted to deploy access-om2 Prerelease pr135-10 with commit 67027dd

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr135-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr135-10

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-pr135-10 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.02.003
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 · 2026-02-18T22:58:24Z

🚀 Attempted to deploy access-om2 Prerelease pr135-10 with commit cefcacd

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr135-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr135-10

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-pr135-10 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.02.003
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.

Release 2026.02.000 v2

anton-seaice had a problem deploying to Gadi Prerelease February 17, 2026 04:04 — with GitHub Actions Failure

anton-seaice had a problem deploying to Gadi Prerelease February 17, 2026 22:00 — with GitHub Actions Failure

anton-seaice temporarily deployed to Gadi Prerelease February 17, 2026 23:15 — with GitHub Actions Inactive

anton-seaice temporarily deployed to Gadi Prerelease February 17, 2026 23:35 — with GitHub Actions Inactive

anton-seaice mentioned this pull request Feb 18, 2026

Add default CICE5 builds when using CMake ACCESS-NRI/access-spack-packages#383

Merged

anton-seaice temporarily deployed to Gadi Prerelease February 18, 2026 05:07 — with GitHub Actions Inactive

anton-seaice changed the title ~~Rc 2026.02.000 v2~~ Release 2026.02.000 v2 Feb 18, 2026

anton-seaice force-pushed the rc-2026.02.000-v2 branch from 8f5f1ac to 8fc280c Compare February 18, 2026 22:01

anton-seaice marked this pull request as ready for review February 18, 2026 22:01

anton-seaice requested a review from dougiesquire February 18, 2026 22:01

anton-seaice had a problem deploying to Gadi Prerelease February 18, 2026 22:03 — with GitHub Actions Failure

anton-seaice mentioned this pull request Feb 18, 2026

Release 2026.02.000 #133

Closed

2 tasks

anton-seaice had a problem deploying to Gadi Prerelease February 18, 2026 22:03 — with GitHub Actions Failure

dougiesquire previously approved these changes Feb 18, 2026

View reviewed changes

spack.yaml Outdated Show resolved Hide resolved

anton-seaice dismissed dougiesquire’s stale review via 67027dd February 18, 2026 22:52

anton-seaice and others added 3 commits February 19, 2026 09:54

Update to CICE5 @2026.01.000 using CMake

c9d2b39

Apply suggestion from @dougiesquire Co-authored-by: Dougie Squire <dougiesquire@gmail.com>

Update access-generic-tracers to 2026.01.000

19f616d

Update release version to 2026.02.000

cefcacd

anton-seaice force-pushed the rc-2026.02.000-v2 branch from 67027dd to cefcacd Compare February 18, 2026 22:54

anton-seaice temporarily deployed to Gadi Prerelease February 18, 2026 22:56 — with GitHub Actions Inactive

dougiesquire approved these changes Feb 18, 2026

View reviewed changes

anton-seaice merged commit 1f9b94f into main Feb 18, 2026
9 checks passed

anton-seaice deleted the rc-2026.02.000-v2 branch February 18, 2026 23:08

anton-seaice temporarily deployed to Gadi Prerelease February 18, 2026 23:08 — with GitHub Actions Inactive

CodeGat pushed a commit that referenced this pull request Feb 19, 2026

Merge pull request #135 from ACCESS-NRI/rc-2026.02.000-v2

f03dc3b

Release 2026.02.000 v2

CodeGat restored the rc-2026.02.000-v2 branch February 19, 2026 02:50

CodeGat mentioned this pull request Feb 19, 2026

Release 2026.02.000 v2 (Recreated) #137

Merged

2 tasks

CodeGat temporarily deployed to Gadi Prerelease February 19, 2026 03:05 — with GitHub Actions Inactive

dougiesquire deleted the rc-2026.02.000-v2 branch February 19, 2026 03:49

Conversation

anton-seaice commented Feb 17, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 17, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Feb 17, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Feb 17, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

anton-seaice commented Feb 17, 2026

Uh oh!

github-actions bot commented Feb 17, 2026

Uh oh!

anton-seaice commented Feb 17, 2026

Uh oh!

github-actions bot commented Feb 17, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

anton-seaice commented Feb 18, 2026

Uh oh!

github-actions bot commented Feb 18, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

anton-seaice commented Feb 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 18, 2026

🖥️ Gadi Deployment ❌

Uh oh!

anton-seaice commented Feb 18, 2026

Uh oh!

github-actions bot commented Feb 18, 2026

🖥️ Gadi Deployment ❌

Uh oh!

anton-seaice commented Feb 18, 2026

Uh oh!

github-actions bot commented Feb 18, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Feb 18, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

anton-seaice commented Feb 18, 2026

Uh oh!

dougiesquire left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

anton-seaice commented Feb 18, 2026

Uh oh!

github-actions bot commented Feb 18, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Feb 18, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

anton-seaice commented Feb 17, 2026 •

edited by github-actions bot

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

anton-seaice commented Feb 18, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️