Update comments in spack.yaml for clarity

[chrisb13]

Closes #174

---

When doing the Upstream model component update it's become clear it would be good to also tweak the docs and related files.

Related:

ACCESS-NRI/access-om3-configs#1029
ACCESS-NRI/access-om3-configs#1028

---

🚀 The latest prerelease access-om3/pr175-2 at 6c9717f is here: #175 (comment) 🚀

[github-actions]

The model version in the ./spack.yaml has not been updated.
You can update it manually.

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr175-1 with commit 7e2fc7d

🖥️ Gadi Deployment ❌

[chrisb13]

@anton-seaice, you can see related changes as we discussed this morning, here https://github.com/ACCESS-NRI/access-om3-configs/pull/1029/changes#diff-500018106e11ef4f5550f8f886da5c57f97d0f01831a04414ba55e63c00996a1

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr175-1 with commit 7e2fc7d

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.001 as a Release (when merged).
• pr175-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/pr175-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-pr175-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.08.003
• 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.

[github-actions]

The model version in the ./spack.yaml has not been updated.
You can update it manually.

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr175-2 with commit 7e2fc7d

🖥️ Gadi Deployment ❌

[anton-seaice]

Thanks @chrisb13 - PRs to main trigger a new deployment, so best to bundle this into the next deplyoment (aka the new OM3 build)

[chrisb13]

Thanks @chrisb13 - PRs to main trigger a new deployment, so best to bundle this into the next deployment (aka the new OM3 build)

Okay. So do you mean that I should cherry pick these commits? Or maybe I could just re-name this branch to the new build?

Related: do I base the new build on the main branch of this repo'?

[github-actions]

The model version in the ./spack.yaml has not been updated.
You can update it manually.

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr175-2 with commit 6c9717f

🖥️ Gadi Deployment ❌

[anton-seaice]

Or maybe I could just re-name this branch to the new build?

This is good as the change is minor. (If it was better to review several pieces of the next deployment seperately, there could be a dev branch which we use several PRs to change, and then at the end have a PR from dev into main)

Related: do I base the new build on the main branch of this repo'?

Yep

[chrisb13]

Or maybe I could just re-name this branch to the new build?

This is good as the change is minor. (If it was better to review several pieces of the next deployment seperately, there could be a dev branch which we use several PRs to change, and then at the end have a PR from dev into main)

Ok. I think the name should be 2026.01.000? Is this an example of the process?

I think when I re-name, this will close this PR but I'll then just open a new one.

[anton-seaice]

Yeah - that looks like the PR from last time.

I think the name should be 2026.01.000?

This is the right version to use for now in the spack.yaml. The github workflow will pick up that version and use it for a tag when doing the deployment. There are sometimes conflicts between branch and tag names, so id use a "release candidate" name or something else for the branch (e.g. rc-2026.01.000)

[chrisb13]

e.g. rc-2026.01.000

Done. New PR.