>people can force an update by removing their bower_components directory. you may need to remove from cache too, but that's the price you pay for that.

Yes. One will have to do ```bower cache clean```, however, the idea was to make it more transparent for developers.

>This is why I think using git shas or similar is a better strategy for people, but this task shouldn't do that for them

Do you mean using referencing a dependency by its SHA? Well, in this case, while it is guaranteed that a dependency will never change, it will not allow us to use snapshot versions either.

Anyway, as it was mentioned above, the goal of this pull request is to allow for having snapshot dependencies. We agreed to introduce the ```overwriteVersion``` configuration option. If is set to ```true```, then:

1.  A git tag will be in the form of ```bowerJSON.version+[timestamp]```, e.g. ```1.0.0-SNAPSHOT+111111`
2. If there are already tags, whose name starts with ```bowerJSON.version``` (e.g. ```1.0.0-SNAPSHOT+2222``` they will be deleted.

If ```overwriteVersion``` is not present or set to ```false```, then the plug-in will continue in its normal mode, that is, a tag will not be suffixed and none of the tags will be removed.

@caitp, I apologise if that behaviour wasn't clear from the very beginning. I just wonder if it can still align with the ```grunt-bower-release``` roadmap.