1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
|
#!/bin/bash
set -o pipefail
set -e
cd "$(dirname "$0")/.."
if ! [ -f ~/.pypirc ]; then
echo "ERROR: For this script to work you need a working ~/.pypirc file:"
echo " https://docs.python.org/3/distutils/packageindex.html#pypirc"
exit 1
fi
# Ask user to consider updating the README.rst Output section.
cat <<EOM
Please consider updating the Output section of README.rst before releasing.
This includes the ptop screenshot, scale your window to 90x24 before shooting it.
Answer yes at this prompt to verify that the Output section is complete.
EOM
read -r -p "Output section complete: " MAYBE_YES
if [ "$MAYBE_YES" != "yes" ]; then
echo
echo "Please update the Output section of README.rst and try this script again."
exit 0
fi
# Verify that we're on the python branch
if [ "$(git rev-parse --abbrev-ref HEAD)" != "python" ]; then
echo "ERROR: Releases can be done from the 'python' branch only"
exit 1
fi
# Verify there are no outstanding changes
if [ -n "$(git status --porcelain)" ]; then
echo "ERROR: There are outstanding changes, make sure your working directory is clean before releasing"
echo
git status
exit 1
fi
# List changes since last release
echo
echo "List of changes since last release:"
git log --color --format="format:%Cgreen%s%Creset (%ad)%n%b" --first-parent "$(git describe --abbrev=0)..HEAD" | cat
echo
echo "=="
echo "Last version number was $(git describe --abbrev=0), enter new version number."
# If not, we'll for some reason get 0.0.0 versioned files in dist/, which
# messes up out Pypi publishing.
echo "Version number must be on 1.2.3 format for the buildscripts to work."
read -r -p "New version number: " NEW_VERSION_NUMBER
# Validate new version number
if [ -z "$NEW_VERSION_NUMBER" ]; then
echo "Empty version number, never mind"
exit 0
fi
if ! echo "$NEW_VERSION_NUMBER" | grep -E '^[0-9]+[.][0-9]+[.][0-9]+$'; then
echo "Version number not in 1.2.3 format, never mind"
exit 0
fi
echo Please enter "$NEW_VERSION_NUMBER" again:
read -r -p " Validate version: " VALIDATE_VERSION_NUMBER
if [ "$NEW_VERSION_NUMBER" != "$VALIDATE_VERSION_NUMBER" ]; then
echo "Version numbers mismatch, never mind"
exit 1
fi
# Get release message from user
cat <<EOM
==
You will now get to compose the release description for Github,
write something nice! And remember that the first line is the
subject line for the release.
EOM
read -r -p "Press ENTER when ready: "
git tag --annotate "$NEW_VERSION_NUMBER"
# Lots of automation from here on, be verbose for troubleshooting purposes
set -x
find . -name 'px*.whl' -delete
# Test and build the release so we know it works before we release it
tox
# Mark new release on Github.
#
# Note that this implicitly triggers uploads to Homebrew and PyPI through GitHub
# actions configured in .github/workflows.
git push --tags
cat <<EOM
==
Now, go to the Releases page on GitHub...
https://github.com/walles/px/releases
... and click your new release, click the "Edit tag" button, then attach
your "px.pex" file that was just built to the release.
After uploading that file, press "Publish release".
EOM
read -r -p "Press ENTER when done: "
cat <<EOM
==
Your release should now be visible here:
* https://github.com/walles/px/releases/latest
* https://formulae.brew.sh/formula/px (or at least there should be a PR open)
* https://pypi.python.org/pypi/pxpx
EOM
|
