A GitHub Action for releasing a Python project to PyPI after every relevant, merged PR.

The purpose of this action is to make project maintenance as easy as possible for PyPI-hosted projects by removing the need to decide when to release. By releasing after every relevant PR is merged, not only is the question of whether to release gone, but the overhead of remembering how to even do a release and then preparing one is also gone. It also allows for releases to occur in situations where you may not have easy access to a checkout or machine set up to make a release (e.g. merging a PR from your phone). As well, contributors will be able to benefit from their hard work much faster than having to wait for the gathering of multiple changes together into a single release.

Do note that this action is not designed to work for all projects. This action is very opinionated and is not expected to be a fit for all Python projects.

1. Update the version number according to a label on the merged PR
2. Update the changelog based on the commit message
3. Commit the above updates
4. Build the sdist and wheel
5. Upload to PyPI
6. Create a release on GitHub

Due to the fact that this action commits back to the repository, you cannot have srequired status checks on PRs as that prevents direct commits from non-admins.

name: Release

on:
  push:
    branches:
      - master

jobs:
  test:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - uses: actions/setup-python@v2
      with:
        python-version: '3.8'

    # ... more steps for testing.

  lint:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - uses: actions/setup-python@v2
      with:
        python-version: '3.8'

    # ... more steps for linting.

  release:
    needs: [test, lint]

    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - uses: brettcannon/release-often@v1
      with:
        changelog-path: doc/CHANGELOG.rst  # XXX Update as appropriate!
        pypi-token: ${{ secrets.PYPI_TOKEN }}
        github-token: ${{ secrets.GITHUB_TOKEN }}

Required: The path to the changelog file. Paths must end in one of the following extensions to denote the file format:

• .md
• .rst

Leaving this input out will disable automatic changelog updating.

The changelog file is expected to either be empty or have the appropriate header.

The PyPI API token for this project. It is strongly suggested that you create a token scoped to just this project.

Leaving this input out will disable uploading to PyPI.

Required: The GitHub access token (i.e. ${{ secrets.GITHUB_TOKEN }}). This allows for committing changes back to the repository.

Based on which of the following labels are applied to a PR, update the version number:

• impact-breaking to bump the major version
• impact-feature to bump the minor version
• impact-bugfix to bump the micro version
• impact-post-release to add/bump the post version
• impact-project to make no change

Supported build tools:

• Poetry
• flit

The first line of the commit message is used as the entry in the changelog for the change. The PR and the author of the change are mentioned as part of the changelog entry.

Input:

• Path to changelog file

Supported changelog formats are:

• .md
• .rst

Build the project's sdist and wheel using PEP 517.

Once the above changes are made and the build artifacts can be successfully built, commit the changes that were made.

With the checkout and repository in the appropriate state for release, the code can now be built and pushed to PyPI.

Input:

• PyPI API token

Finally, when everything is live, create a release on GitHub to both tag the release in the repository and store the artifacts uploaded to PyPI. The name of the release is the version prepended by v and the body of the release is the changelog entry.