Note: we saw failures in the PyPI release process after merging this PR. I believe this is due to the fact that the repository had not yet been renamed to almanack prior to the GitHub release being published which as a result caused a failure in alignment with PyPI trusted publisher settings (which expect almanack in the naming of the repo). On retrying this after renaming the repo, GH Actions containers appear to re-use the original repo name when re-running them. I expect that this might change on subsequent releases and new actions jobs being created. We'll give this a try after the next PR merge.
Originally posted by @d33bs in https://github.com/software-gardening/almanack/issues/43#issuecomment-2161529836