Closed GadgetSteve closed 5 years ago
Hello Gadget Steve,
That's a good suggestion. Do you already have some info for such a release script?
Best luc
Unfortunately it was done as a part of my work so I cannot share directly but basically:
dulwich
) to determine what the last one was and use the appropriate next from semantic_version
- this gives me my new version information.re
magic in each of the files that are in the impacted list, (obviously I have marked the places that this is needed with something re
-able).New Major Release 3.0.0
and use that as the message for a git commit all (I found this easier to do via a subprocess.call
than via dulwich
but we have some strange security settings),zipfile
and(Obviously several of these steps are skipped for test builds).
In the case of release builds I automatically copy the zipped files to a file share, (Box in our case), and while I would love to automate the uploading to the internal github releases area against the tag the aforementioned security settings have defeated me so far so I open the default browser to the required location and the file explorer to the zip process output directory so all I need to do is select the latest tag and drag & drop the zip file(s).
README.md States: Current version is 0.5.7 this is incorrect the latest version at the time of this ticket is 0.5.8 and should this ticket be addressed it will be at least 0.5.9
I suggest creating a release script which updates the "current" version everywhere needed, (i.e. README.md, metadata, embedded version, etc. and then creates the github release and does the publishes to pypi all in a single step.