Set up auto to automate releases

[jwodder]

Closes #73.

This PR also needs to be accompanied by the following changes:

• [x] Create the necessary labels for auto by running GH_TOKEN=... auto create-labels in a copy of this repository containing .autorc
• [x] All PRs merged since the previous release should receive appropriate labels
• [x] An auth token for uploading assets for the pyout project to PyPI must be saved as a secret named "PYPI_TOKEN"

[vsoch]

In case it helps I use this workflow to release to pypi, after logging in and creating a project specific token. https://github.com/singularityhub/singularity-hpc/blob/main/.github/workflows/release.yaml.

I still like control of when the release happens, but with automated release notes that is just a few clicks!

[yarikoptic]

I still like control of when the release happens, but with automated release notes that is just a few clicks!

if I got the accent on when correctly, we will still have that control -- releases would be triggered by merging PRs with release label.

[yarikoptic]

@vsoch - would you mind adding me (yarikoptic) to maintainers of tributors on PyPI?

[vsoch]

Are you sure we don't need a video call before to verify you are who you are? How do I know someone hasn't hijacked yarikoptic's account? :thinking:

Just kidding, that would be ridiculous :)

Done.

[yarikoptic]

It all depends, it all depends... Thank you!

[yarikoptic]

oh, need to get back to this one too

[yarikoptic]

@jwodder I do not see release and only see skip-release. Does it mean that we would release after each PR merge?

[jwodder]

@yarikoptic The lack of a release label is a side-effect of f4b1a56b41bb3eac2971e12ed11988abbc8d3734. The label will have to be created manually.

[yarikoptic]

gotcha -- thanks, made a label