invalid semver tags prevent use of backbone.paginator with Bower

[baer]

Bower only allows you to specify a tag if the tag is a valid semver e.g. 0.8.0. If you cannot provide it with a valid version it will ONLY allow you to checkout latest which for a production site is not acceptable.

The versioning in the package.json files are correct but because the tags themselves are of the form 0.8 and not 0.8.0 bower is disallowing tags from this repo. There are open issues in the Bower project that talk about this but until they are fixed I'd like to ask if it would be acceptable to publish new tags or do a minor rev of the last few releases to make them compatible as this drastically limits community adoption.

Thanks for all your great work!

41
141
433
275

[leonardehrenfried]

My suggestion would be to release a v0.8.1 with the correct semver tag immediately.

@addyosmani @wyuenho Any objections?

[leonardehrenfried]

The old tags also start with a v. Is that problematic as well?

[baer]

The v is actually not part of the tag so the actual tags out there are 0.8, 0.7 etc. Releasing a 0.8.1 tag would do the trick for most people though It would be nice to give those people with more sensitive QA needs / higher impact systems the option to use bower without forcing an upgrade by releasing a x.x.1 for all tags but 0.8.1 would be a great start.

[wyuenho]

The v is actually not part of the tag so the actual tags out there are 0.8, 0.7 etc. Releasing a 0.8.1 tag would do the trick for most people though It would be nice to give those people with more sensitive QA needs / higher impact systems the option to use bower without forcing an upgrade by releasing a x.x.1 for all tags but 0.8.1 would be a great start.

What @baer said :)

Just make a new tag.

[leonardehrenfried]

Sorry to be pedantic but I want to get this right: If you look here you'll see that the git tag does include a v. Does bower ignore a preceding letter? Or should the tag just be the naked version?

[baer]

@Lenniboy is right, for some reason I thought it was github that was appending the "v" to the tag but after checking out the repo and running git tag -l they all do in fact have a "v" in the front. So that said a correct tag would just be simply.

0.8.1

[wyuenho]

The thing is, you can put any semvar inside bower.json and you can submit it. You can even search for it from bower. It just can't check out the repo if it doesn't have such a tag.

Regardless, like @baer said, you can just retag all the existing tags and submit a bower.json with an actual semvar version number and everything should just work as intended.

[leonardehrenfried]

Ok, I will release a version 0.8.1 right now. I'm a little reluctant to retag all previous releases without Addy's go-ahead.

If people haven't been able to use the previous versions with Bower anyway is there really a need to add the semver-compliant tags anyway?

[leonardehrenfried]

0.8.1 has been released.

[addyosmani]

You have my permission to retag all previous releases. There may be a chance it's going to cause dependency resolution issues for users but I would like us to be able to resolve our longer-term Bower/versioning problems.

Thanks for releasing 0.8.1, @Lenniboy!

[wyuenho]

Question: where does the bower.json live now? I don't see it in the repo.

[baer]

Bower doesn't need it's dependency file to be called bower.json. All the info is in package.json

[baer]

Thanks for the release! Just pulled the project in successfully with Bower this morning.