diff --git a/.github/workflows/python-app.yml b/.github/workflows/python-app.yml index f55ee52..a47e3d1 100644 --- a/.github/workflows/python-app.yml +++ b/.github/workflows/python-app.yml @@ -40,10 +40,10 @@ jobs: steps: - uses: actions/checkout@v3 - - name: Set up Python 3.9 + - name: Set up Python 3.11 uses: actions/setup-python@v4 with: - python-version: 3.9 + python-version: 3.11 cache: 'pip' - name: Install dependencies run: | diff --git a/ReleaseNotes.md b/ReleaseNotes.md index c1f5908..df54069 100644 --- a/ReleaseNotes.md +++ b/ReleaseNotes.md @@ -1,7 +1,14 @@ -# Dave's Release Notes +# Release Process -Use Github's release mechanism to create a new release. -Do not do it from the command line. Use the web interface. +Create an annotated tag for the release, then push it to the repository. For +example: -Dave is dumb. Do not be Dave. +```sh +git tag -a v0.4.5 -m "Release v0.4.5" +git push upstream v0.4.5 +``` + +Replace `upstream` with the name of the remote you push releases to. Pushing a +`v*` tag triggers the publish workflow, which creates a GitHub release titled +`Release v0.4.5` and generates its release notes. diff --git a/requirements.txt b/requirements.txt index c10f7a2..1024006 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1,4 +1,4 @@ comment_parser pyspellchecker -bibtexparser +bibtexparser<2 requests