chore(bower): dropped support for bower

since bower itself recommends migrating away

BREAKING CHANGE: Bower is no longer supported

howto_release.markdown

@@ -6,13 +6,10 @@ To release version x.y.z:
 - bump version of peer dependency *AND* devDependency for traverson in package.json to latest
 - bump version in package.json to x.y.z
 - bump version in package-lock.json to x.y.z
-- bump version in bower.json to x.y.z
 - npm install
 - `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-hal.*` (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`

readme.markdown

@@ -31,7 +31,6 @@ Installation
 ### Browser
 
 * If you are using npm and [Browserify](http://browserify.org/): Just `npm install traverson traverson-hal --save` and include `traverson` and `traverson-hal` via `require` (see below), then browserify your module as usual - browserify will include Traverson and its dependencies for you .
-* If you are using [Bower](http://bower.io): `bower install traverson traverson-hal--save`
 * Otherwise you can grab a download from the [latest release](https://github.com/traverson/traverson-hal/releases/latest). None of files includes Traverson itself, so you will also have to download a Traverson release.
     * `traverson-hal.min.js`: Minified build with UMD. This build can be used with an AMD loader like RequireJS or with a script tag (in which case it will register `TraversonJsonHalAdapter` in the global scope). **If in doubt, use this build.**
     * `traverson-hal.js`: Non-minified build with UMD. Same as above, just larger :-)