Add conda and pip internal uploads

[brynpickering]

This is a flavour of the central Arup composite action to enable uploading packages to https://packages.arup.com for pip packages and https://packages.arup.com/conda for conda packages. This allows internal Arup projects to be installable by pip install or conda install. For conda, it just requires a new channel listing: -c https://packages.arup.com/conda.

In both cases, repos that use the "internal" package destination need to have access to the Arup packages self-hosted runner via a service-now request. I could add that to the README in this repo or in the https://github.com/arup-group/cookiecutter-pypackage/ docs. Or both!

[mfitz]

I could add that to the README in this repo or in the https://github.com/arup-group/cookiecutter-pypackage/ docs. Or both!

Both would be good.

[mfitz]

Looks good, @brynpickering, and definitely a useful thing to have.

Do you have an example of using one of these amended workflows from a repo to publish a package into the private conda and/or pip artefact repos?

[brynpickering]

It's based on a workflow I set up in https://github.com/arup-group/HeatNet_tool (recent run: https://github.com/arup-group/HeatNet_tool/actions/runs/12409338105/job/34642751052).

Ideally though we'd have it run for one of the CML internal repos using this PR branch. @neilmt might have a suitable repo, if I remember correctly!

[brynpickering]

Ones we could test this on (as they were created with the template and are internal):

https://github.com/arup-group/transaka
https://github.com/arup-group/gbpop
https://github.com/arup-group/texaspop

@gac55 @neilmt would there be any benefit to one of these being available for pip/conda install within the Arup network? Or, conversely, is there a reason why one of these should not be available beyond those with current access to the internal repo?

[neilmt]

@brynpickering Transaka is WIP but yes it'd be great to implement this for it.

[mfitz]

👍