I have angular 1.2.3 and I want to upgrade to 1.2.7
> cat bower.json
...
\"dependencies\": {
\"json3\": \"~3.2.4\",
\"jquery\": \"~1.9.1\",
I think your dependencies are preventing you from updating angular in isolation. E.g., look at bower_components/angular-route/bower.json
. You will see a specific version of angular listed as a dependency ("1.2.3") and not a ~
/"reasonably close" specifier" ("~1.2.3"). So you are trying to update just angular, but the farthest that bower can take your angular is the current version since you have other packages that depend on exactly that version.
If you do bower update
then bower will have the opportunity to update all your packages, including angular-route and other packages that are holding angular back. The updates to these packages will now allow bower to update angular while satisfying dependencies. Also, I think if you identified all those packages depending on a specific angular version (you can see dependencies with bower list
) and passed them as arguments like bower update angular angular-mocks angular-resource angular-route angular-sanitize...
then bower could also perform the update.
I think the problem is about this
"angular": "~1.2.3"
https://github.com/isaacs/node-semver/
"Reasonably close to 1.2.3".
so you should change it with
"angular": "1.2.7"
UPDATE: (it's in the comment but I think it's better point it out)
Note that you can’t pass a package name to the update command and only update that individual package: it will still update ’em all. You can get the latest version of a single package by running bower install ; it will just over-write the version you currently have