From d33dbdb4834a398b2f956bcf5bb55ab508d27fb0 Mon Sep 17 00:00:00 2001 From: Kevin Kirsche Date: Thu, 11 Jun 2015 22:54:47 -0400 Subject: [PATCH] Don't touch bower version Per bower/bower.json-spec@a325da3 this is useless. I'm in the process of making PR's to every bower repo to get that removed forever Also their maintainer says they probably won't ever use it: http://stackoverflow.com/questions/24844901/bowers-bower-json-file-version-property --- xyz | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/xyz b/xyz index 2bfd62e..407d9b4 100755 --- a/xyz +++ b/xyz @@ -9,7 +9,7 @@ This involves updating the version number in package.json, committing this change (along with any staged changes), tagging the commit, pushing to the remote git repository, and finally publishing to the public npm registry. -If present, bower.json and component.json are updated along with package.json. +If present, component.json is updated along with package.json. Options: @@ -155,7 +155,6 @@ inc() { } inc package.json -inc bower.json inc component.json run "git commit --message '$message'"