jQuery 1.12.1 and 2.2.1 Released

Posted on by

As the jQuery team prepares for a 3.0 final release, we continue to maintain the 1.12 and 2.2 branches. These two patch releases fix a few bugs and improve stability. The most significant bug fix involved a problem with the .position() method, which affected how jQuery UI tooltips were positioned in Internet Explorer.

We do not expect this release to have any breaking changes, but if you do encounter bugs in upgrading from the previous version, please let us know.

Download

You can include these files directly from the jQuery CDN if you like, or copy them to your own local server. The 1.x branch includes support for IE 6/7/8 and the 2.x branch does not.

https://code.jquery.com/jquery-1.12.1.js
https://code.jquery.com/jquery-1.12.1.min.js

https://code.jquery.com/jquery-2.2.1.js
https://code.jquery.com/jquery-2.2.1.min.js

These updates are already available as the current versions on npm and Bower. Information on all the ways to get jQuery is available at https://jquery.com/download/. Public CDNs receive their copies today, please give them a few days to post the files. If you’re anxious to get a quick start, use the files on our CDN until they have a chance to update.

Full changelogs

2.2.1GitHub changelog

1.12.1GitHub changelog

Many thanks to all of you who participated in this release by testing, reporting bugs, or submitting patches, including Oleg Gaidarenko, Michał Gołębiowski, Zack Hall, Todor Prikumov, and Devin Wilson.

13 thoughts on “jQuery 1.12.1 and 2.2.1 Released

  1. Thanks for the update, and the work by those that have contributed to this great project over the years. I am curious to how the jQuery performs on a mobile browser right now. Are the references in the above comments towards performance referring to a browser on desktop/laptop computer or mobile browser? Where is a good place to test the performance for jQuery on your own?

  2. … and today I’m wondering what the future is for jQuery. I have stopped using it two years ago, when we dropped support for IE8. There is no londer need to use it for DOM manipulation (the browser DOM api is enough) and for other tasks sometimes I resort to lodash. Current frameworks no longer use it either… I don’t miss it, and neither do most of my peer developers.

  3. John G. on said:

    It’s been more than a week, and the Google CDN still doesn’t have the new versions. Any insights?

  4. Are the references in the above comments towards performance referring to a browser on desktop/laptop computer or mobile browser?