Repository navigation
Commit 05c468e
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -0,0 +1,19 @@ | |||
| 1 | + all: | ||
| 2 | + @grep -Ee '^[a-z].*:' Makefile | cut -d: -f1 | grep -vF all | ||
| 3 | + | ||
| 4 | + clean: | ||
| 5 | + rm -rf build/ dist/ | ||
| 6 | + | ||
| 7 | + release: clean | ||
| 8 | + # Check if latest tag is the current head we're releasing | ||
| 9 | + echo "Latest tag = $$(git tag | sort -nr | head -n1)" | ||
| 10 | + echo "HEAD SHA = $$(git rev-parse head)" | ||
| 11 | + echo "Latest tag SHA = $$(git tag | sort -nr | head -n1 | xargs git rev-parse)" | ||
| 12 | + @test "$$(git rev-parse head)" = "$$(git tag | sort -nr | head -n1 | xargs git rev-parse)" | ||
| 13 | + make force_release | ||
| 14 | + | ||
| 15 | + force_release: clean | ||
| 16 | + @which -s twine || echo "Twine not installed, run pip install twine first" | ||
| 17 | + git push --tags | ||
| 18 | + python setup.py sdist bdist_wheel | ||
| 19 | + twine upload dist/* | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -70,31 +70,15 @@ You can watch me fix issues or implement new features [live on Twitch][twitch-ch | |||
| 70 | 70 | ||
| 71 | 71 | ### How to make a new release | |
| 72 | 72 | ||
| 73 | - * assure `changes.rst` is up-to-date | ||
| 74 | - * put new version into `VERSION` file | ||
| 75 | - * run `./setup.py sdist` | ||
| 76 | - * On https://pypi.python.org | ||
| 77 | - - Click `GitPython` (and pray it will not timeout) | ||
| 78 | - - Lucky ? Click `edit` on the last version, and copy the main description text | ||
| 79 | - to your clipboard - it's needed later. | ||
| 80 | - - On top of that page, click the `PKG file` button or drag & drop the one from | ||
| 81 | - `./GitPython.egg-info/PKG-INFO` on it. Then click the `add ...` button to | ||
| 82 | - create a new version. | ||
| 83 | - - Paste the previously copied description text into the description field, and click the `add information` button on the very bottom of the page. | ||
| 84 | - - Click `GitPython` again and then click `files` of the newly created version. | ||
| 85 | - - Select `source package` in the dropdown, then choose or drag & drop | ||
| 86 | - `./dist/GitPython-<version>.tar.gz` onto the file path. | ||
| 87 | - - Click the `upload` button. | ||
| 88 | - * Run `git tag <version>` to mark the version you just uploaded to pypi. | ||
| 89 | - * Run `git push --tags origin master` to publish the changes. | ||
| 90 | - * finally, set the upcoming version in the `VERSION` file, usually be incrementing | ||
| 91 | - the patch level, and possibly by appending `-dev`. Probably you want to `git push` once more. | ||
| 73 | + * Update/verify the version in the `VERSION` file | ||
| 74 | + * Update/verify that the changelog has been updated | ||
| 75 | + * Commit everything | ||
| 76 | + * Run `git tag <version>` to tag the version in Git | ||
| 77 | + * Run `make release` | ||
| 78 | + * Finally, set the upcoming version in the `VERSION` file, usually be | ||
| 79 | + incrementing the patch level, and possibly by appending `-dev`. Probably you | ||
| 80 | + want to `git push` once more. | ||
| 92 | 81 | ||
| 93 | - *NOTE:* At the time of writing, pypi wouldn't hear my prayers and did timeout on | ||
| 94 | - me, which is why button names are just *guesses*. It's advised to update this text | ||
| 95 | - next time someone manages to publish a new release to a system so firmly rooted in | ||
| 96 | - the past. | ||
| 97 | - | ||
| 98 | 82 | ### LICENSE | |
| 99 | 83 | ||
| 100 | 84 | New BSD License. See the LICENSE file. | |
0 commit comments