You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Uses the github release as the source of truth. Updates the package.json and various configs with the proper version.
This means that the new versions will not be checked into the repo, but they will be deployed properly. I am not sure if that is problematic
read -p "Have you updated the javascript version in https://github.com/BranchMetrics/documentation/edit/master/ingredients/web_sdk/_initialization.md ?" -n 1 -r
128
-
echo
47
+
npm publish
129
48
130
49
echo"Post-release sanity checks."
131
50
read -p "Can you visit https://cdn.branch.io/branch-$VERSION.min.js ?" -n 1 -r
132
51
echo
133
52
read -p "Is https://cdn.branch.io/example.html using the right version number $VERSION?" -n 1 -r
134
53
echo
135
54
read -p "Is https://www.npmjs.com/package/branch-sdk using the right version number $VERSION?" -n 1 -r
136
-
echo
137
-
138
-
echo
139
-
if [[ $REPLY=~ ^[Yy]$ ]]
140
-
then
141
-
echo"Ok"
142
-
fi
143
-
144
-
echo"Last step, run:"
145
-
echo" git push; git push origin $VERSION"
146
-
147
-
echo
148
-
echo"Remember to check https://github.com/BranchMetrics/Smart-App-Banner-Deep-Linking-Web-SDK/tree/$VERSION/CHANGELOG.md "
149
-
echo
150
-
echo"Remember to ping @jed on slack about this release "
0 commit comments