I have a very small repo in which I do all dev work in the master branch and use tags as "stable" points in history.
I guess by default Bower seems to fetch the latest tagged version of a repo. I'm trying to get the most recent commit in the master branch.
I've tried running all these, in every conceivable order:
bower cache-clean mypackage
bower install mypackage --force-latest
bower install mypackage --force --force-latest
bower install mypackage --force
I've also tried adding latest
to my bower.json file:
"dependencies": {
"mypackage": "latest"
}
And then running:
bower update mypackage
No matter what it seems to always get the latest tagged state.
How do I get the latest, most up-to-date, untagged state of the project?
adds this:
Specify a git commit SHA instead of a version:
Example:
You can also specify a branch instead of a SHA, but that's generally not recommended unless it's in development and you control all the parts.
If you are using a bower.json file you specify the latest version of a branch with a line in either the dependencies or devDependencies as appropriate for your project configuration:
Then when you run
bower install
the latest version of that branch is installed. That would be branchbootstrap3
ofangular-ui
in this example.using bower.json:
where
Yes, you can point to the git url, or use name/repo shorthand (for github repos):
bower.json
More in the docs
As @roi noted in the comments, you can use the
--save
flag to automatically add dependencies tobower.json
, e.g.bower install terinjokes/docker-npmjs --save
You can install a branch in Bower > 1.0.0:
More details at https://github.com/bower/bower/issues/107#issuecomment-22352689.