Bower does not update dependencies with branch as version

[JostBaron]

I have a git repository in my dependencies:

  "devDependencies": {
    "template": "user@domain.tld:reponame.git#develop"
  },

This should always fetch the newest version of the branch "develop" (when using bower update), but it doesn't. To get the newest version after someone pushed to it, I have to clean the bower cache, delete the directory in in my bower_components-folder, and do a bower update.

[mdasberg]

It sees the that the commit hash has changed, but does not actually do anything with it :(

[sheerun]

I can confirm. Bower updates package only after bower cache clean.

This is definitely connected with #1211 where overwriting cache were disabled. bower 1.3.1 is OK.

We should probably introduce --no-cache flag for such cases or disable caching of moving branches.

@benschwarz What do you think?

[benschwarz]

I think a user calling bower update is explicit enough that they want to "fetch" remote repositories.
Why don't we remove the cache for bower update?

[sheerun]

@benschwarz What cache? All cache or selectively? It is weird.

Besides as described in #1211 removing cache in any way produces lot of concurrency problems.

I think that entirely disabling cache for moving versions (like branches) is the best option.

[benschwarz]

I think that entirely disabling cache for moving versions (like branches) is the best option.

👍

[MiguelMadero]

I think that entirely disabling cache for moving versions (like branches) is the best option.

👍

I'm having the same problem. Apart from bower cache clean is there another (better) workaround?

[sheerun]

For now only downgrading to 1.3.1

[MiguelMadero]

Thanks. That sounds good.

[sheerun]

Fixed on master. It'll be released in 1.3.3