-
Notifications
You must be signed in to change notification settings - Fork 9
Automate update of bower distribution #10
Comments
One this is completed, I can list bower as an option in the getting started guide (and elsewhere). |
This would be great! |
@feryardiant Is this something you think you will be able to complete in the near future? At this point, Fine Uploader is at 5.11.8 and the bower version is still at 5.11.0. It would be great if we could get this to auto-update whenever a new Fine Uploader version is tagged. Perhaps that could be handled by travis-ci. Also, I'd like to get Fine Uploader distributed on bower as fine-uploader, instead of fineuploader-dist. That is covered in #9. |
Hi. My apology. I've planned to use github hooks to automate our bower distribution via travis but recently I have no much time to complete it. I'll back to it very soon. Pada 11 Sep 2016 6.44 AM, Ray Nicholus [email protected] menulis: @feryardiant Is this something you think you will be able to complete in the near future? At this point, Fine Uploader is at 5.11.8 and the bower version is still at 5.11.0. It would be great if we could get this to auto-update whenever a new Fine Uploader version is tagged. Perhaps that could be handled by travis-ci. Also, I'd like to get Fine Uploader distributed on bower as fine-uploader, instead of fineuploader-dist. That is covered in #9. — |
Current version is 5.13, bur not released here :( |
@jedie While I realize bower is still used by some, it's hard to justify not using npm anymore. I would suggest you consider using npm to pull down all dependencies that are not strictly tied to bower (Fine Uploader being one such dependency). |
It would be great if all of the work required to update the bower dist could happen automatically, by Travis-CI. It seems like the best time to do this is when a new version of Fine Uploader is tagged in the fine-uploader repo. This likely will require changes in the fine-uploader repo as well (such as to the build scripts and the travis config).
The text was updated successfully, but these errors were encountered: