Release automation

[lucianopaz]

Closes #162

This PR adds two things.

1. It adds a release.yml that serves as a template for release notes. It establishes the same labeling convention that is used in PyMC.
2. It adds a workflow that is only triggered by publishing a release. This will first create the sdist and bdist for the package, test that installing them provides the package with the same version as the one set in the commit tag, then attempts to upload to test.pypi, and if successful, finally uploads to pypi.

[drbenvincent]

Nice!

At the moment the release notes are really easy with the automated GitHub release notes button, producing things like this with zero effort.

Do you know if or how that would change with the .github/release.yml file?

[lucianopaz]

With the release.yml, your release notes would be divided into sections:

• Major Changes 🛠
• New Features 🎉
• Bugfixes 🐛
• Documentation 📖
• Maintenance 🔧

The first 4 sections would require you to provide an appropriate label to the PR that is being merged. The PRs that don't have any of those special labels would be listed under the maintenance section. The list of first time contributors will still show up without any changes.

[twiecki]

Can we merge this?

[drbenvincent]

In an ideal world we'd update CONTRIBUTING.md.

[drbenvincent]

Do I understand correctly that all this needs in order to work properly is the following tags to exist?

• no releasenotes
• major (this is the only one that doesn't exist at this point)
• enhancement
• bug
• everything else is labelled as maintenance?

And the labels that are relevant are ones on the PR's, not on the issues that they may close?

[drbenvincent]

Currently this goes through my personal pypi account. Do we want to move that over to PyMC Labs pypi account, or shall I just enter my personal secrets.PYPI_API_TOKEN on GitHub?