Bump the minor version of jquery-rails for new minor versions of jQuery
Closed this issue · 2 comments
Not an issue per se, but I wonder if it would be better to bump the minor version of jquery-rails when a new minor version of jquery is bundled?
For example, 1.0.17 of jquery-rails included jQuery 1.7. If it were tagged as 1.1.0 instead, we could more easily manage the version of jQuery we want in our Gemfile. It's not currently possible to bundle update and get the latest patch release of a particular jQuery version.
# We want jQuery to 1.6.x
gem 'jquery-rails', '~>1.0'
Of course, this is tricky to manage sensibly for jquery-rails because it essentially bundles up a bunch of different libraries.
What I'm wondering aloud is whether there is a more meaningful way to tag jquery-rails releases. What does everyone think?
I have to agree here. It was a HUGE (and painful) surprise to find that my Gemfile which specifies '~>1.0' allowed a behind-the-scenes upgrade from 1.6.4 to 1.7. A big jump to an incompatible jquery version should not happen via a patch-version level change to this gem. This does not follow semantic versioning protocol: http://semver.org/
That's a good point, I'll keep this in mind in the future.