We don't intend to go back and re-tag all the releases that predate our start of Bower support. Can you suggest a solution that doesn't require re-tagging?

Tagging a 1.8.3+2 which includes the jquery.js should fix the problem

Okay, I should add that we don't intend to go back and re-tag releases each time someone asks for an old release. Can you suggest a solution that doesn't require re-tagging?

Hey Dave,

The "jquery.js" file in the root seems to have been a convention since the release of 1.2.3 (in 1.8.3 you guys started including the minified file). Also, the commit message on the "jquery.js" file reads on every release since 1.2.3 "Include distribution in release tag". This indicates pretty clearly to an API consumer that the file can be depended on making it an API breaking change and not ok to remove in a suffixed maintenance release.

Another issue is that semantic versioning indicates 1.8.3 can match 1.8.3+1, so Bower or not, it makes it difficult to depend on 1.8.3 specifically using any sort of automation. It might be worth noting that "+" versions, I've observed, are only generally used as part of a semantic version suffix such as alpha, beta or rc. I could be wrong, though, since the semver specification doesn't explicitly say anything about that.

For what it's worth, I believe that tagging a 1.8.3+2 release is the right thing to do and is in the best interest of the greater jQuery community.

I know it's not particularly kosher, but we've already rebuilt all of the tags that corresponded to Component tags. Rebuilding this one would not be very difficult. I've thrown up a sample here.

Ok, I was totally confused. My local master didn't have the updated tags that timmywil pushed, which I just fixed. So if it's just about fixing this one tag, that seems okay.

Fixed. https://github.com/jquery/jquery/commit/e7136682e89f358915994f4a2167fcdea395358e

Thankyou

Thankyou, much appreciated