I want to update js-jquery to jQuery 3 (it is currently 2). So, I'm going to follow the rename procedure to rename js-jquery to js-jquery2. Afterwards, instead of retiring js-jquery, I'll update it to version 3. This ensure a proper upgrade path for packages which need version 2, specifically. For now, I've pushed an update to add the following Provides to the current js-jquery package, so other packages can start depending on js-jquery2 instead, while I prepare a js-jquery2 package for review: Provides: js-jquery2 = %{version} Provides: js-jquery2-static = %{version} These updates have been submitted to Bodhi for epel7, f24, f25, f26 for testing. If you depend on js-jquery and your package won't work with jQuery3, please test these updates and change your Requires/Recommends/Suggests to js-jquery2 instead of js-jquery (or depend on jquery, with a specific version, like rubygem-jquery-rails does). I'm only planning on doing the rename/update to F26 and Rawhide. If somebody needs jQuery 3 for EPEL7, I might be willing to do that later, but I'm not updating F24 and F25. The following packages depend on js-jquery in F26 and Rawhide: beets-plugins jpype-doc js-jquery-datetimepicker js-jquery-file-upload js-jquery-iframe-transport js-jquery-jstree js-jquery-knob js-jquery-mousewheel js-jquery-noty js-php-date-formatter js-tag-it koschei-frontend mkdocs python-systemd-doc python-txaio-doc python2-sphinxcontrib-programoutput python3-sphinxcontrib-programoutput I don't know if any of these actually need to be updated to Requires: js-jquery2, or if they will continue to work with jQuery 3. I'll leave it to the maintainers to check. Thanks for your attention (and especially for those who helped me understand the package rename/upgrade path process).