TEST: Custom Scopes via versions.json

[CodeGat]

Background

This is a test for the new custom-scopes stuff, based on the infra-v8 branch. See ACCESS-NRI/build-cd#335

The PR

• [no ci] infra: Update to v8
• [no ci] infra: Update spack version to v1.1, update manifest schema to 2-0-0
• [no ci] spack.yaml: Dedent list elements for spack-style manifests
• [no ci] spack.yaml: Add reserved definitions
• [no ci] spack.yaml: Use toolchains
• Change entrypoint workflow version to 334-spack-v1-migration-config-removal-from-manifest_TEST

---

🚀 The latest prerelease access-test/pr61-5 at 7f192f8 is here: #61 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-test Prerelease pr61-1 with commit 760c6e2

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-test Prerelease pr61-1 with commit 41561ce

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-test Prerelease pr61-2 with commit 46978dc

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.09.000 as a Release (when merged).
• pr61-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr61-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/1.1/spack in the access-test-pr61-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 1.1
• spack/spack-packages version 8ed34337e15d759890b68682d704aa55dd243537
• access-nri/access-spack-packages version api-v2
• access-nri/spack-config version 2025.11.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]

🚀 Attempted to deploy access-test Prerelease pr61-3 with commit cbd9d46

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-test Prerelease pr61-4 with commit 010d9b0

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.09.000 as a Release (when merged).
• pr61-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr61-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-test-pr61-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 8ed34337e15d759890b68682d704aa55dd243537
• access-nri/access-spack-packages version api-v2
• access-nri/spack-config version 2025.11.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]

🚀 Attempted to deploy access-test Prerelease pr61-5 with commit 7f192f8

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.09.000 as a Release (when merged).
• pr61-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr61-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-test-pr61-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 8ed34337e15d759890b68682d704aa55dd243537
• access-nri/access-spack-packages version api-v2
• access-nri/spack-config version 2025.11.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.