Symfony bower vesionized packages -

official symfony2 documentatation writes:

bower not have "lock" feature, means there's no guarantee running bower install on different server give exact assets have on other machines. more details, read article checking in front-end dependencies.

but can init bower.json , in file have dependencies precized version like

#bower.json "dependencies": {     "html5shiv": "3.7.1",     "bootstrap-sass-official": "3.3.0", } 

so if use bower install should install precized version of packages. dont understand bower.lock neeeded ?

symfony website warns situation.

for example there lock file in composer in way when define php dependency in composer.json following.

"require": {     "php": ">=5.3.3", } 

it means php version should @ least 5.3.3 or above.

in situation lock file important make server's synced.

but in requirements there no need wonder about. because defined spesific minor version '3.3.0' without operator '~' no worries if using exact versions.

but then, if vendors doesn't follow semantic versioning there may sync problem again. instance : if changes change tagged version while deploying. rare case shouldn't worry too.