... when a new version is released upstream.
It should be as easy as changing the "version" and "sha256" values in setup.cfg file:
| [download] |
| ; OpenType Sanitizer version that is downloaded from setup.py |
| version = 7.1.8 |
| ; expected SHA-256 of the downloaded tarball. E.g. you can calculate it with: |
| ; $ shasum -a 256 ots-X.X.X.tar.xz |
| sha256 = 7e0e3233e7cb07073a48d48fbfccf7a09b1b68fdd60189213c0cf76f59bd2bec |
commit that change, create a git tag with the same version number (always keep a leading v, e.g. v7.1.9 in the git tag name), and push the tag. The bots will do the rest.
... when a new version is released upstream.
It should be as easy as changing the "version" and "sha256" values in
setup.cfgfile:ots-python/setup.cfg
Lines 1 to 6 in dc1c925
commit that change, create a git tag with the same version number (always keep a leading
v, e.g.v7.1.9in the git tag name), and push the tag. The bots will do the rest.