Autorelease workflow draft

[Qwlouse]

Adds a github actions workflow that triggers automatically on a version change and uploads the new version to pypi.
(based on https://github.com/marketplace/actions/pypi-github-auto-release )

Not sure how to best test this.

[AdamGleave]

One way to test it is by uploading to Test PyPI on every push. imitation has it set up this way. The tricky part is that will fail if there are duplicate version numbers. You can either ensure version numbers are unique (by automatically generating them and including the Git ID as part of it), or just accept it'll fail but check that it fails for the "right" reason (duplicate version number not something different.

[thequilo]

@AdamGleave uploading to the PyPI test servers for every push seems a bit too much, doesn't it? But I don't really see another option for testing the release workflow, either.

[AdamGleave]

Pushing to Test PyPI on every commit is the recommended approach by https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/ Although as discussed I've run into problems with it, so take that recommendation with a grain of salt.

An alternative would be to push to test PyPI on commits to a specific branch?

[thequilo]

What branch would that be? If we use the master (i.e., on every PR merge), the frequency of uploads would be much smaller, but errors might slip through unnoticed. If it's the recommended way to upload to the test server on every commit, then it's probably not too much

[thequilo]

@Qwlouse can you also provide an API token for the test server?

[vnmabus]

@AdamGleave uploading to the PyPI test servers for every push seems a bit too much, doesn't it? But I don't really see another option for testing the release workflow, either.

Man, put the condition as:

on:
  release:
    types: [published]

and do the releases manually in Github!

A new Sacred release is necessary for it to work with the recent NumPy version.

[vnmabus]

See https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries as an example.

[thequilo]

Okay, you convinced me that it's necessary to publish a new release to PyPI (and I am myself very annoyed by the fact that the latest release is basically unusable). Since we're not going to get a token on the test server, a new release on PyPI is more important than testing. Let's hope that everything goes well first try!