How to cut a Briefcase release#
The release infrastructure for Briefcase is semi-automated, using GitHub Actions to formally publish releases.
This guide assumes that you have an
upstream remote configured on your
local clone of the Briefcase repository, pointing at the official repository.
If all you have is a checkout of a personal fork of the Briefcase repository,
you can configure that checkout by running:
$ git remote add upstream https://github.com/beeware/briefcase.git
The procedure for cutting a new release is as follows:
Check the contents of the upstream repository’s main branch:
$ git fetch upstream $ git checkout --detach upstream/main
Check that the HEAD of release now matches upstream/main.
Ensure that the release notes are up to date. Run:
$ tox -e towncrier -- --draft
to review the release notes that will be included, and then:
$ tox -e towncrier
to generate the updated release notes.
Build the documentation to ensure that the new release notes don’t include any spelling errors or markup problems:
$ tox -e docs-lint,docs
Ensure that there is a version branch for the new Briefcase version in every template that Briefcase will use at runtime:
Tag the release, and push the branch and tag upstream:
$ git tag v1.2.3 $ git push upstream HEAD:main $ git push upstream v1.2.3
Pushing the tag will start a workflow to create a draft release on GitHub. You can follow the progress of the workflow on GitHub; once the workflow completes, there should be a new draft release, and an entry on the Test PyPI server.
Confirm that this action successfully completes. If it fails, there’s a couple of possible causes:
The final upload to Test PyPI failed. Test PyPI is not have the same service monitoring as PyPI-proper, so it sometimes has problems. However, it’s also not critical to the release process; if this step fails, you can perform Step 6 by manually downloading the “packages” artifact from the GitHub workflow instead.
The test apps fail to build. This is likely because you forgot to branch one (or more) of the templates mentioned in Step 3. If this happens, you can correct the missing template, and re-run the action through the GitHub Actions GUI.
Something else fails in the build process. If the problem can be fixed without a code change to the Briefcase repository (e.g., a transient problem with build machines not being available), you can re-run the action that failed through the GitHub Actions GUI. If the fix requires a code change, delete the old tag, make the code change, and re-tag the release.
Create a clean virtual environment, install the new release from Test PyPI, and perform any pre-release testing that may be appropriate:
$ python3 -m venv testvenv $ . ./testvenv/bin/activate (testvenv) $ pip install --extra-index-url https://test.pypi.org/simple/ briefcase==1.2.3 (testvenv) $ briefcase --version briefcase 1.2.3 (testvenv) $ #... any other manual checks you want to perform ...
Log into ReadTheDocs, visit the Versions tab, and activate the new version. Ensure that the build completes; if there’s a problem, you may need to correct the build configuration, roll back and re-tag the release.
Edit the GitHub release to add release notes. You can use the text generated by towncrier, but you’ll need to update the format to Markdown, rather than ReST. If necessary, check the pre-release checkbox.
Double check everything, then click Publish. This will trigger a publication workflow on GitHub.
Wait for the package to appear on PyPI.
Congratulations, you’ve just published a release!
If anything went wrong during steps 4-10, you will need to re-start from step 4 with a new version number. Once the release has successfully appeared on PyPI (or Test PyPI), it cannot be changed; if you spot a problem in a published package, you’ll need to tag a completely new release.