Skip to content

Next release (2026.04.002) - #218

Merged
dougiesquire merged 4 commits into
mainfrom
next-release
Aug 18, 2026
Merged

dougiesquire merged 4 commits into
mainfrom
next-release

Conversation

@dougiesquire

@dougiesquire dougiesquire commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Changes for the next release of ACCESS-ESM1.6. I haven't set the version yet because I'm not 100% on what will be included.

Currently includes:

  • Update to MOM5 2026.02.001
    • Includes corrections to some diagnostics' units, and fixes for compiling with GCC
    • This was intended to be done in the previous release but was accidentally removed
  • Update to FMS 2025.08.001
    • Added control of date stamp formatting in diagnostic filenames
  • Update to UM7 2026.04.002
    • gfortran related fixes for UM 2025

🚀 The latest prerelease access-esm1p6/pr218-4 at c91a243 is here: #218 (comment) 🚀

@dougiesquire dougiesquire self-assigned this Aug 14, 2026
@dougiesquire

Copy link
Copy Markdown
Collaborator Author

@MartinDix, @blimlim are there other changes that are ready to be included here?

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p6 Prerelease pr218-1 with commit e6eae45

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.04.001 as a Release (when merged).
  • pr218-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr218-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-esm1p6-pr218-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.

@dougiesquire

Copy link
Copy Markdown
Collaborator Author

!update-configs

@github-actions

Copy link
Copy Markdown

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-esm1.6-configs

Configurations Requested

Configurations requested from profile default:

  • dev-amip

  • dev-esm-historical

  • dev-esm-piControl

  • dev-historical

  • dev-piControl

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-ESM1.6/actions/runs/31764288445

Comment thread spack.yaml Outdated
@blimlim

blimlim commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

I've just checked with @anton-seaice and @MartinDix - once the new UM version is in it sounds like there aren't any further changes at the moment, and this one should be ready to go!

Co-authored-by: Spencer Wong <88933912+blimlim@users.noreply.github.com>
@dougiesquire

Copy link
Copy Markdown
Collaborator Author

!update-configs

@github-actions

Copy link
Copy Markdown

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-esm1.6-configs

❌ One or more errors occurred with the workflow

Configurations Requested

Configurations requested from profile default:

  • dev-amip

  • dev-esm-historical

  • dev-esm-piControl

  • dev-historical

  • dev-piControl

Pull Requests Opened/Updated

No PRs were opened/updated

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

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p6 Prerelease pr218-2 with commit 085dc96

🖥️ Gadi Deployment ❌

@dougiesquire

Copy link
Copy Markdown
Collaborator Author

@blimlim, I think um7@2026.04.002 needs to be added to the spack package?

@blimlim

blimlim commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

Oh my bad I missed that step, I'll add that now

@dougiesquire

Copy link
Copy Markdown
Collaborator Author

All good - happy to review

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p6 Prerelease pr218-3 with commit e12fd76

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.04.001 as a Release (when merged).
  • pr218-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr218-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-esm1p6-pr218-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
  • ACCESS-NRI/upstream-spack-packages version access/v1.1
  • access-nri/access-spack-packages version 2026.08.009
  • 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.

@dougiesquire

Copy link
Copy Markdown
Collaborator Author

!update-configs

@github-actions

Copy link
Copy Markdown

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-esm1.6-configs

Configurations Requested

Configurations requested from profile default:

  • dev-amip

  • dev-esm-historical

  • dev-esm-piControl

  • dev-historical

  • dev-piControl

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-ESM1.6/actions/runs/32091414647

@dougiesquire
dougiesquire marked this pull request as ready for review August 18, 2026 03:20
@dougiesquire dougiesquire changed the title Next release (2026.??.???) Next release (2026.04.002) Aug 18, 2026
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p6 Prerelease pr218-4 with commit c91a243

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p6 Prerelease pr218-4 with commit c91a243

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.04.002 as a Release (when merged).
  • pr218-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr218-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-esm1p6-pr218-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
  • ACCESS-NRI/upstream-spack-packages version access/v1.1
  • access-nri/access-spack-packages version 2026.08.009
  • 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.

@blimlim blimlim left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dougiesquire, the versions all look correct to me

@dougiesquire
dougiesquire merged commit 047c910 into main Aug 18, 2026
17 of 18 checks passed
@dougiesquire
dougiesquire deleted the next-release branch August 18, 2026 03:45

This branch was previously deployed

1 inactive deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants