commit fc115e1f66a35399bacf1d3f327d5f17e81c4adc
parent 76051a6ac2fb60dbc79d3fde8405169b4c3a41bf
Author: Martin von Gagern <gagern@ma.tum.de>
Date: Sun, 22 Jan 2017 15:28:37 +0100
Obtain updated README by using a checkout
As the dist directory isn't available on the original branch, we cant use
its files to update the SRI hashes. Checking out from the release tag is
therefore the better option. A checkout will automatically stage its files.
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/release.sh b/release.sh
@@ -139,9 +139,9 @@ if [ ! -z "$NEXT_VERSION" ]; then
# Refer to the just-released version in the documentation of the
# development branch, too. Most people will read docs on master.
- node update-sri.js "${VERSION}" README.md contrib/*/README.md
+ git checkout "v${VERSION}" -- README.md contrib/*/README.md
- git add package.json bower.json README.md contrib/*/README.md
+ git add package.json bower.json
git commit -n -m "Bump $BRANCH to v$NEXT_VERSION-pre"
git push origin "$BRANCH"
