chore(bower): dropped support for bower

since bower itself recommends migrating away

BREAKING CHANGE: Bower is no longer supported

Author: travi

bower.json

@@ -7,12 +7,9 @@ To release version x.y.z:
 - npm i
 - bump version in package.json to x.y.z (should match the used traverson version, at least the major and minor number)
 - bump version in package-lock.json to x.y.z (should match the used traverson version, at least the major and minor number)
-- bump version in bower.json to x.y.z
 - `npm run build` (to create a fresh browser build, also make sure all tests pass etc.)
-- First release? Then `bower register package-name git://github.com/user/repo.git`
 - `git commit -am"release x.y.z" && git push`
 - `npm publish`
-- `git checkout -b release-x.y.z` (to create the release branch, required for bower)
 - `git add -f browser/dist/traverson-angular.*` (to add the build artifacts to the release branch)
 - `git commit -m"add build artifacts for release"`
 - `git push origin release-x.y.z`
@@ -23,7 +20,7 @@ To release version x.y.z:
   - empty description
   - add all four JS files from browser/dist as "binaries" to the release
   - Publish release
-- Why not just create a tag from the branch via git? Because we want to add the build artifacts to the GitHub relase as attachments (for users neither using npm or bower). This is only possible if the release was created via GitHub's web interface. Normal git tags show up as releases there too, but you can't add attachments or edit the release afterwards. Releases created via the web interface create a git tag automatically, however.
+- Why not just create a tag from the branch via git? Because we want to add the build artifacts to the GitHub relase as attachments (for users not using npm). This is only possible if the release was created via GitHub's web interface. Normal git tags show up as releases there too, but you can't add attachments or edit the release afterwards. Releases created via the web interface create a git tag automatically, however.
 - `git checkout master`
 - `git branch -D release-x.y.z`
 - `git push origin :release-x.y.z`

howto_release.markdown

@@ -37,10 +37,6 @@ You can grab a download from the [latest release](https://github.com/traverson/t
 * `traverson.external.min.js`: Minified require/external build. Created with browserify's `--require` parameter and intended to be used (required) from other browserified modules, which were created with `--external traverson-angular`. This build could be used if you use browserify but do not want to bundle traverson-angular and Traverson with your own browserify build but keep it as a separate file.
 * `traverson.external.js`: Non-minified require/external build, same as before, just larger.
 
-### Bower
-
-`bower install traverson-angular --save`
-
 Usage
 -----