tools
tools copied to clipboard
TheKevJames
Automate nox version upgrade
This change introduces a Github action to create a pull request whenever a new version of nox is detected on PyPi.
The Github action does the following:
- installs the latest version of nox from PyPi
- spits out that version into a requirements.txt file
- uses peter-evans/create-pull-request@v3 github action to create a pull request if any files have changed. Thus, if a new version of nox has been found on PyPi the requirements.txt file will be detected as a changed file and a pull request will be created with the updated nox version.
If desired the settings for the pull request creation can be changed to auto merge. I'll leave that decision up to you @TheKevJames
I just noticed that you are already using renovate in this repo. So I have changed my PR to use a simple renovate config to manage the nox version.
Hi @seanblumenfeld, thanks for the contribution! Unfortunately, there's a bit missing here before this will help out solving the problem entirely: we need to be able to correctly tag the image on dockerhub (and, ideally, in github) to denote releases. If you happen to be aware of any method of accomplishing this, that would be fantastic! As-is, bumping the version number in the dockerfile is only one of the pieces of the puzzle.
Dockerhub also recently changed its pricing on autobuilds, so orthogonally from this request I need to find some time to update my CI accordingly; I'll likely need to switch over to build&pushing images from CircleCI rather than relying on Dockerhub. That's probably irrelevant for this particular PR, but if it gives you any ideas on the tagging thing I'd be happy to hear them!
