Skip to content
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

bower install installs an old version, because of bower naming convention #520

Closed
guyzi opened this issue Jun 28, 2015 · 4 comments
Closed

Comments

@guyzi
Copy link

guyzi commented Jun 28, 2015

Names that contain '-' are considered pre-released version and not the latest version and thus not downloaded when using bower install.

See this issue for details:
bower/bower#782

I've solved this issue by creating a tag with a name such as 0.4.1

@mattgrande
Copy link

Did you manually create that tag? I'm trying to get 0.4.0-hotfix.1 into my app, and it keeps installing 0.4.

@guyzi
Copy link
Author

guyzi commented Jul 14, 2015

Yeah exactly. I've created a tag for my own fork though. This is exactly the 'bug', a tag with '-' in its name is not considered the latest version, but a prereleased version (see this bower/bower#782)

@mattgrande
Copy link

I changed my bower.json to have the explicit version number (ie, "leaflet.markercluster": "0.4.0-hotfix.1"), and that got it working.

I was trying to say "0.4.0-hotfix.1 or greater," but couldn't get that to work, unfortunately.

@danzel
Copy link
Member

danzel commented Dec 22, 2015

This isn't really a markercluster bug.
There will be a new pre-release version soon for 1.0.0 compatibility. Watch #528

@danzel danzel closed this as completed Dec 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants