Core: Remove support for jQuery 4.x

Changes:

* Core: Remove support for jQuery 4.x

* Core: Don't reimplement deprecated but not removed APIs

    This will save space and avoid potential divergence from Core.

    To minimize risk, this only handles APIs still present in jQuery 4.x.

* Attributes: Update warnings.md to not mention jQuery 4.0

* Build: Rename more `main`s to `3.x-stable`s

* Event: Reimplement APIs deprecated in jQuery 3.0/3.1

    This fixes tests with 3.0/3.1 slim builds.

* Tests: Test on jQuery 3.1.1.slim in non-BrowserStack browser tests

    jQuery <3.2.0 doesn't include the deprecated module in the slim build so it
makes sense to test on one of these versions in slim mode even on PRs.

* Build: Stop testing on iOS 10

    As of January 2025, iOS 10 is a tier 4 device on BrowserStack:
    https://www.browserstack.com/device-tiers
    That leads to devices with this iOS version often not being available and
    failing our tests. Remove it from the test matrix. Also, add comments explaining
    the status of tests on various iOS versions, including iOS 7 that we stopped
    testing on a long time ago.

* Build: Update a vulnerable dependency

* Core: Update the package.json description

    Indicate this version of Migrate helps with updating jQuery to 3.x, not 3.0+.

* Docs: Link to jQuery Browser Support page in README.md

Closes gh-554
Ref gh-555
Ref jquery/jquery#5606

Author: mgol

.github/workflows/browser-tests.yml

@@ -4,7 +4,7 @@ on:
   pull_request:
   push:
     branches:
-      - main
+      - 3.x-stable
 
 env:
   NODE_VERSION: 22.x

.github/workflows/browserstack-git.yml

@@ -1,9 +1,9 @@
-name: Browserstack (Core 3.x)
+name: Browserstack
 
 on:
   push:
     branches:
-      - main
+      - 3.x-stable
   # Once a week every Tuesday
   schedule:
     - cron: "12 2 * * 2"
@@ -51,9 +51,19 @@ jobs:
           - '__iOS_13'
           - '__iOS_12'
           - '__iOS_11'
-          - '__iOS_10'
+
+          # iOS 10 is a tier 4 device as of January 2025 and its availability
+          # is poor, leading to frequent test timeouts. Skip testing on it.
+          # See https://www.browserstack.com/device-tiers
+          # - '__iOS_10'
+
+          # Versions below are not officially supported by BrowserStack as
+          # they use emulators instead of real devices. We include them as
+          # long as they still work.
           - '__iOS_9'
           - '__iOS_8'
+          # iOS 7 emulators no longer work properly
+          # - '__iOS_7'
     steps:
       - name: Checkout
         uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
@@ -79,6 +89,6 @@ jobs:
 
       - name: Test
         run: |
-          npm run test:unit -- -v -c jtr-3.x.yml \
+          npm run test:unit -- -v -c jtr-ci.yml \
             --browserstack "${{ matrix.BROWSER }}" \
             --run-id ${{ github.run_id }} \

.github/workflows/browserstack-3.x.yml .github/workflows/browserstack.yml

@@ -3,7 +3,7 @@ name: Filestash
 on:
   push:
     branches:
-      - main
+      - 3.x-stable
 
 permissions:
   contents: read # to fetch code (actions/checkout)
@@ -47,5 +47,5 @@ jobs:
 
       - name: Upload to Filestash
         run: |
-          rsync dist/jquery-migrate.js filestash@"${{ secrets.FILESTASH_SERVER }}":jquery-migrate-git.js
-          rsync dist/jquery-migrate.min.js filestash@"${{ secrets.FILESTASH_SERVER }}":jquery-migrate-git.min.js
+          rsync dist/jquery-migrate.js filestash@"${{ secrets.FILESTASH_SERVER }}":jquery-migrate-3.x-git.js
+          rsync dist/jquery-migrate.min.js filestash@"${{ secrets.FILESTASH_SERVER }}":jquery-migrate-3.x-git.min.js

.github/workflows/filestash.yml

@@ -47,7 +47,7 @@ Make sure you have reproduced the bug with all browser extensions and add-ons di
 
 ### Try the latest version of jQuery Migrate
 
-Bugs in old versions of jQuery Migrate may have already been fixed. In order to avoid reporting known issues, make sure you are always testing against the [latest build](https://releases.jquery.com/git/jquery-migrate-git.js). We cannot fix bugs in older released files, if a bug has been fixed in a subsequent version of jQuery Migrate the site should upgrade.
+Bugs in old versions of jQuery Migrate may have already been fixed. In order to avoid reporting known issues, make sure you are always testing against the [latest build](https://releases.jquery.com/git/jquery-migrate-3.x-git.js). We cannot fix bugs in older released files, if a bug has been fixed in a subsequent version of jQuery Migrate the site should upgrade.
 
 ### Simplify the test case
 
@@ -78,16 +78,16 @@ Change directory to the newly created dir `jquery-migrate/`:
 $ cd jquery-migrate
 ```
 
-Add the jQuery Migrate `main` as a remote (e.g. `upstream`):
+Add the jQuery Migrate `3.x-stable` as a remote (e.g. `upstream`):
 
 ```bash
 $ git remote add upstream [email protected]:jquery/jquery-migrate.git
 ```
 
-Get in the habit of pulling in the "upstream" main to stay up to date as jQuery Migrate receives new commits:
+Get in the habit of pulling in the "upstream" `3.x-stable` to stay up to date as jQuery Migrate receives new commits:
 
 ```bash
-$ git pull upstream main
+$ git pull upstream 3.x-stable
 ```
 
 Install the necessary dependencies:

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-![CI Status](https://github.com/jquery/jquery-migrate/actions/workflows/node.js.yml/badge.svg?branch=main)
+![CI Status](https://github.com/jquery/jquery-migrate/actions/workflows/node.js.yml/badge.svg?branch=3.x-stable)
 
 #### NOTE: To upgrade to jQuery 3.0, you first need version 1.12.x or 2.2.x. If you're using an older version, first upgrade to one of these versions using [jQuery Migrate 1.x](https://github.com/jquery/jquery-migrate/tree/1.x-stable#readme), to resolve any compatibility issues. For more information about the changes made in jQuery 3.0, see the [upgrade guide](https://jquery.com/upgrade-guide/3.0/) and [blog post](https://blog.jquery.com/2016/06/09/jquery-3-0-final-released/).
 
@@ -11,14 +11,14 @@ That way you can spot and fix what otherwise would have been errors, until you n
 
 The following table indicates which jQuery Migrate versions can be used with which jQuery versions:
 
-| jQuery version | jQuery Migrate version  |
-|----------------|-------------------------|
-| 1.x            | 1.x                     |
-| 2.x            | 1.x                     |
-| 3.x            | 3.x / 4.x<sup>[1]</sup> |
-| 4.x            | 3.x / 4.x<sup>[1]</sup> |
+| jQuery version | jQuery Migrate version |
+|----------------|------------------------|
+| 1.x            | 1.x                    |
+| 2.x            | 1.x                    |
+| 3.x            | 3.x                    |
+| 4.x            | 4.x                    |
 
-[1] NOTE: jQuery Migrate 4.x only supports the same browser as jQuery 4.x does. If you need to support Edge Legacy, Internet Explorer 9-10 or iOS 7+ (and not just 3 latest versions), use jQuery Migrate 3.x.
+Each jQuery Migrate version supports the same browsers that the jQuery version used with it. See the [jQuery Browser Support page](https://jquery.com/browser-support/) for more information.
 
 ## Usage
 
@@ -40,7 +40,7 @@ The production build is minified and does not generate console warnings. It will
 | Debugging enabled | <p align="center">✓</p> |  |
 | Minified |  | <p align="center">✓</p> |
 | Latest release (*may be hotlinked if desired*) | [jquery-migrate-3.5.2.js](https://code.jquery.com/jquery-migrate-3.5.2.js) | [jquery-migrate-3.5.2.min.js](https://code.jquery.com/jquery-migrate-3.5.2.min.js) |
-| \* Latest work-in-progress build | [jquery-migrate-git.js](https://releases.jquery.com/git/jquery-migrate-git.js) | [jquery-migrate-git.min.js](https://releases.jquery.com/git/jquery-migrate-git.min.js) |
+| \* Latest work-in-progress 3.x build | [jquery-migrate-3.x-git.js](https://releases.jquery.com/git/jquery-migrate-3.x-git.js) | [jquery-migrate-3.x-git.min.js](https://releases.jquery.com/git/jquery-migrate-3.x-git.min.js) |
 
 
 \* **Work-in-progress build:** Although this file represents the most recent updates to the plugin, it may not have been thoroughly tested. We do not recommend using this file on production sites since it may be unstable; use the released production version instead.
@@ -50,7 +50,7 @@ The production build is minified and does not generate console warnings. It will
 
 The development version of the plugin displays warnings in the browser console. Older browsers such as IE9 doesn't support the console interface. No messages will be generated unless you include a debugging library such as [Firebug Lite](https://getfirebug.com/firebuglite) before including the jQuery Migrate plugin. Developers can also inspect the `jQuery.migrateWarnings` array to see what error messages have been generated.
 
-All warnings generated by this plugin start with the string "JQMIGRATE". A list of the warnings you may see are in [warnings.md](https://github.com/jquery/jquery-migrate/blob/main/warnings.md).
+All warnings generated by this plugin start with the string "JQMIGRATE". A list of the warnings you may see are in [warnings.md](https://github.com/jquery/jquery-migrate/blob/3.x-stable/warnings.md).
 
 
 ## Migrate Plugin API
@@ -69,7 +69,7 @@ This plugin adds some properties to the `jQuery` object that can be used to prog
 
 `jQuery.migrateDeduplicateWarnings`: By default, Migrate only gives a specific warning once. If you set this property to `false` it will give a warning for every occurrence each time it happens. Note that this can generate a lot of output, for example when a warning occurs in a loop.
 
-`jQuery.migrateDisablePatches`: Disables patches by their codes. You can find a code for each patch in square brackets in [warnings.md](https://github.com/jquery/jquery-migrate/blob/main/warnings.md). A limited number of warnings doesn't have codes defined and cannot be disabled. These are mostly setup issues like using an incorrect version of jQuery or loading Migrate multiple times.
+`jQuery.migrateDisablePatches`: Disables patches by their codes. You can find a code for each patch in square brackets in [warnings.md](https://github.com/jquery/jquery-migrate/blob/3.x-stable/warnings.md). A limited number of warnings doesn't have codes defined and cannot be disabled. These are mostly setup issues like using an incorrect version of jQuery or loading Migrate multiple times.
 
 `jQuery.migrateDisablePatches`: Disables patches by their codes.
 

README.md

@@ -22,7 +22,7 @@ var releaseVersion,
 	prompt = enquirer.prompt,
 
 	repoURL = "[email protected]:jquery/jquery-migrate.git",
-	branch = "main",
+	branch = "3.x-stable",
 
 	// Windows needs the .cmd version but will find the non-.cmd
 	// On Windows, also ensure the HOME environment variable is set
@@ -211,7 +211,7 @@ async function publishToNPM( next ) {
 
 function setNextVersion( next ) {
 	updateSourceVersion( nextVersion );
-	updatePackageVersion( nextVersion, "main" );
+	updatePackageVersion( nextVersion, "3.x-stable" );
 	git( [ "commit", "-a", "--no-verify", "-m", "Updating the source version to " + nextVersion ],
 		next );
 }
@@ -281,7 +281,7 @@ function updateReadmeVersion() {
 }
 
 function setBlobVersion( s, v ) {
-	return s.replace( /\/blob\/(?:(\d+\.\d+[^\/]+)|main)/, "/blob/" + v );
+	return s.replace( /\/blob\/(?:(\d+\.\d+[^\/]+)|3.x-stable)/, "/blob/" + v );
 }
 
 function writeJsonSync( fname, json ) {

build/release.js

@@ -2,10 +2,6 @@ version: 1
 
 flags:
   jquery:
-    - git
-    - git.min
-    - git.slim
-    - git.slim.min
     - 3.x-git
     - 3.x-git.min
     - 3.x-git.slim
@@ -18,6 +14,7 @@ flags:
     - 3.3.1
     - 3.2.1
     - 3.1.1
+    - 3.1.1.slim
     - 3.0.0
 
 retries: 1

jtr-3.x.yml jtr-ci.yml

@@ -1,7 +1,7 @@
 {
 	"name": "jquery-migrate",
 	"title": "jQuery Migrate",
-	"description": "Migrate older jQuery code to jQuery 3.0+",
+	"description": "Migrate older jQuery code to jQuery 3.x",
 	"main": "dist/jquery-migrate.js",
 	"version": "3.5.3-pre",
 	"type": "module",