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
Robert Rees edited this page Feb 16, 2015
·
3 revisions
Releasing
Scribe is released via both Bower and NPM. You will need an NPM account and someone in the team will need to add you to the Scribe maintainers list.
Bower
git checkout master
Run ./release.sh [ <newversion> | major | minor | patch | build ] (we use
mversion). (If releasing a
plugin, run the script inside this repository from the plugin’s directory.)
Checkout the dist branch to check you're happy with the compilation result.
If you are, run git push && git push --tags. (The dist tree is for
distribution via Bower).
npm
git checkout master.
Update CHANGELOG.md
Update the version number in package.json
Commit with message of v<number>
git push
Run npm publish
Update example
git checkout gh-pages
git pull
Update necessary dependency versions in bower.json. Check bower ls to see
which components need updating.
bower install
bower prune
git add --update . (don't include untracked files from source Bower
components)
Commit using version number as the message (OR plugin version)