Add a workflow job to automate uploading to testpypi

[ngoldbaum]

Not sure how to make ASCII art matching the other jobs

[timkpaine]

7 is used for adapter tests but grab 8 https://github.com/python-project-templates/cpp/blob/e09da5c92ba382218a558b333975397ffcf901de/.github/workflows/build.yml#L444

[ngoldbaum]

The other issue is that right now the version is static so testpypi won't let us upload a new release with every merged PR. I think scikit-build can work with setuptools_scm - did you ever look at that or any other kind of dynamic version generation from VCS versions?

[ngoldbaum]

For now just set it to only upload if a tag is added.

[timkpaine]

Can you make a tag like deleteme and push to your fork, and show the successful run just to verify

[ngoldbaum]

Thanks for the suggestion to try on my fork. The way I originally configured it there were some bugs. Also I got tripped up on the check for tags that start with v so deleteme doesn't work but vdeleteme does.

Here's the action run https://github.com/ngoldbaum/csp/actions/runs/7879281136/job/21501011776

It failed to upload because my fork isn't a trusted publisher to testpypi for the csp pacakge. Would you like me to temporarily add it to make sure the upload goes through? We can also merge this as-is and debug once we push an e.g. v0.1.0 tag to the main repo.

[trallard]

This looks good to me so I will go ahead and approve @ngoldbaum.
That way we can test the release and iterate as needed

The merge-base changed after approval.

The merge-base changed after approval.

The merge-base changed after approval.

[ngoldbaum]

It's not clear to me why github is saying I'm dismissing stale reviews, it seems to be happening automatically.

[ngoldbaum]

I rebased again, I think if one of you approve it will be mergeable.