Update spack.yaml

[anton-seaice]

Demonstration of build from latest main

[github-actions]

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

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

[github-actions]

🚀 Deploying access-om3 2024.10.0 as prerelease pr16-2

Details and usage instructions

This access-om3 model will be deployed as:

• 2024.10.0 as a Release (when merged).
• pr16-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/pr16-2

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3- environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.10.17

Details

It will be deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2024.07.08
• access-nri/spack-config version 2024.10.17

If this is not what was expected, commit changes to config/versions.json.

[access-hive-bot]

This pull request has been mentioned on ACCESS Hive Community Forum. There might be relevant details there:

https://forum.access-hive.org.au/t/ocean-team-workshop-12-15th-november-2024/3857/7

[CodeGat]

Hey @anton-seaice, due to:

• The update to Prerelease versioning (in which we now use number of deployments rather than number of commits, which allows rebasing), and
• The update to Projections in the spack.yaml

Some of the spack environment names may clash for future deployments in this PR. If possible, can we move this to a new PR, and close this one? Happy to help out if needed.

There are conflicts currently on this branch due to the above, so you'll need to rebase onto main before opening the next PR - let me know if you need a hand!

[anton-seaice]

Demonstration only :)