jQuery UI 1.13.2 released

Posted on by

We’re happy to announce the second patch release to jQuery UI 1.13 is out. It includes a security fix for the Checkboxradio widget, a few localization updates for Datepicker and some fixes for issues submitted by the community. Built jQuery UI files are now included in the npm package; this was important to some CDNs that rely on it as the source of truth.

More details about the security issue fixed:

Please remember jQuery UI is in a maintenance state: we’ll make sure the library is compatible with new jQuery releases and that security issues are fixed but no new significant feature work is planned. We’ll also try to fix important regressions from jQuery UI 1.12.1; older long-standing bugs may not get fixed. Note that this does not affect jQuery Core which is still actively maintained.


File Downloads

Git (contains source files, with @VERSION replaced with 1.13.2, base theme only)

Install via npm

  • npm install jquery-ui@1.13.2

Install via bower

  • bower install jquery/jquery-ui#1.13.2

jQuery CDN

Google Ajax Libraries API (CDN)

Microsoft Ajax CDN (CDN)

Custom Download Builder


See the 1.13 Upgrade Guide for a list of changes that may affect you when upgrading from 1.12.x. For full details on what’s included in this release see the 1.13.2 Changelog.


Thanks to all who helped with this release, specifically: Adam Lidén Hällgren, Christian Oliff, Denny Septian Panggabean, Felix Nagel, James Hinderks, Michał Gołębiowski-Owczarek.


Note: please report bugs to the jQuery UI Bug Tracker; support questions should be posted on Stack Overflow with the jquery-ui tag. Please don’t use comments to report bugs.

If you have feedback on us doing our release for jQuery UI 1.13.2, feel free to leave a comment below. Thank you.

2 thoughts on “jQuery UI 1.13.2 released

  1. Tim Pepper on said:

    I am now getting undefined (reading ‘regional’) from jquery-ui-i18n.min.js. It was working fine in 1.13.1.

  2. Michał Gołębiowski-Owczarek on said:

    Tim: as indicated at the end of the blog post, please report bugs on GitHub, not here.