From a4ceef0db89a7174126f2ffa35ba6750936c93c1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Go=C5=82e=CC=A8biowski-Owczarek?= Date: Mon, 29 Jun 2026 18:53:21 +0200 Subject: [PATCH] Build: Explicitly test on Safari 26, not latest (3.x version) BrowserStack often shares the Safari version included in the next macOS release as soon as that macOS releases a public beta, but there's no indicator in the API that this Safari version is a beta, making JTR pick it up via `Safari_latest`. To avoid this issue, specify Safari versions explicitly. Fortunately, major Safari versions are only released once a year, so the list can usually be updated together with a related iOS yearly major update. Ref jquery/jquery#5857 Ref jquery/jquery#5858 --- .github/workflows/browserstack.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/browserstack.yml b/.github/workflows/browserstack.yml index 694bf38d..3e217d26 100644 --- a/.github/workflows/browserstack.yml +++ b/.github/workflows/browserstack.yml @@ -28,10 +28,10 @@ jobs: matrix: BROWSER: - 'IE_11' - - 'Safari_latest' - # JTR doesn't take into account the jump from Safari 18 to 26, - # so we need to specify versions explicitly. - # See https://github.com/jquery/jquery-test-runner/issues/17 + # BrowserStack makes Safari on beta macOS versions available without marking + # either the OS or the browser as beta, so we have no way to resolve "latest" + # to the lastest stable version. + - 'Safari_26' - 'Safari_18' - 'Chrome_latest' - 'Chrome_latest-1'