www

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README

commit 225baffef41bdae6e5e47a8c43f0bd72fdc0b6ff
parent 4327e85796e343961fa105673a813db091813f8c
Author: Emily Eisenberg <xymostech@gmail.com>
Date:   Fri,  6 Jan 2017 19:47:47 -0800

And make the release script actually work again.

Summary: The previous commit made the `sed` lines do the same thing on mac and
linux. Unfortunately they didn't actually work. Whoops.

Test Plan:
 - Run `./release.sh` a couple times and become horribly confused before
   realizing what's going on.

@kevinb

Diffstat:
Mrelease.sh | 6+++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/release.sh b/release.sh @@ -38,7 +38,7 @@ git add dist/ # Edit package.json and bower.json to the right version (see # http://stackoverflow.com/a/22084103 for why we need the .bak file to make # this mac & linux compatible) -sed -i.bak 's|"version": "[^"]+",|"version": "'$VERSION'",|' package.json +sed -i.bak -E 's|"version": "[^"]+",|"version": "'$VERSION'",|' package.json sed -i.bak -E 's|"version": "[^"]+",|"version": "'$VERSION'",|' bower.json rm -f package.json.bak bower.json.bak @@ -56,8 +56,8 @@ if [ ! -z "$NEXT_VERSION" ]; then git checkout master # Edit package.json and bower.json to the right version - sed -i.bak -e 's|"version": "[^"]+",|"version": "'$NEXT_VERSION'-pre",|' package.json - sed -i.bak -e 's|"version": "[^"]+",|"version": "'$NEXT_VERSION'-pre",|' bower.json + sed -i.bak -E 's|"version": "[^"]+",|"version": "'$NEXT_VERSION'-pre",|' package.json + sed -i.bak -E 's|"version": "[^"]+",|"version": "'$NEXT_VERSION'-pre",|' bower.json rm -f package.json.bak bower.json.bak git add package.json bower.json