-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow a commit hash instead of a semver version (#275) #441
Conversation
The ENOENT errors in the tests are driving me nuts. Async is hard 😖 |
Good luck resolving those ENOENTS! This looks good otherwise. |
All of the individual test suites pass (e.g. Its something to do with the cleanup for one test happening after the set up for another so that some folder (probably the cache) is getting deleted while it is in use. |
Hooray! I worked it out. By hanging the test off the 'checkout' event and calling next() when that happened, the clean up was happening before the package finished installing. Using the 'install' event instead fixes it. |
@satazor Do we want to land this for 0.9.3? |
@wibblymat yes! ship it |
As soon as this gets merged, #275 can be closed. We still need some other member to review this. |
ship it! @satazor Is this already in the rewrite too? |
Allow a commit hash instead of a semver version (#275)
@necolas yes! :D Everything tagged with |
yay, nice work :) |
My attempt at
still produces
I'm using Bower 0.9.2 |
@zakdances it hasn't been released yet. |
when it will be released? |
Released in 0.10.0 https://github.com/bower/bower/blob/master/CHANGELOG.md#0100---2013-07-02 /cc @tiger-seo |
Please note that
|
Worth mentioning that the rewrite/canary does not use |
Sorry, I'm new totally to bower. Is rewrite/canary a new version of bower? |
See: |
Thanks for info. Will drop PR with fix for current architecture |
Please note that when targeting a commit the full hash has to be given. Otherwise it will still say that no branch/tag is found for the given version. |
This PR gets us most of the way to #275, with a caveat.
The resolve step will fail if a valid version cannot be found. If the repo has tags then it will get a version like v0.6.8-284-g1031af3 from
git describe
- i.e. the commit is tagv0.6.8
plus 284 other commits.If there are no tags in the repo, bower looks for
bower.json
to read a version from there.A repo with no tags and no bower.json cannot be installed.
With the rewrite on the horizon it doesn't seem worth the effort to make this perfect. Its up to you guys whether or not you want it before then!