Can we have images that use the UM be internal or private, rather than public?

[CodeGat]

Since UM related builds cannot be public, we cannot at this stage build access-esm1.5 using build-ci.

Investigate the possibility of making these docker images private or internal, and note what kind of credentials one would need to access it as part of a run.

See https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package

[CodeGat]

Notes: Indeed we can make the packages internal (viewable to members of the org) or private (only to people who have access), but it seems that we cannot do this programmatically, only via the GUI.

And even if we can make it private:

If you grant a public repository access to private packages, forks of the repository may be able to access the private packages.

[CodeGat]

Trying a different tack. We will now no longer automatically link the visibility of the package to the access rights of the repository on an organisational level. See https://github.com/organizations/ACCESS-NRI/settings/packages

[CodeGat]

This hasn't seemed to have helped the visibility of the package itself. See https://github.com/ACCESS-NRI/build-ci/pkgs/container/build-cable-intel2021.2.0-2024.06.05