1951479 - Ship Interventions v137.5.0 out-of-band

Status: RESOLVED FIXED

(Web Compatibility :: Interventions, task)

Description

[Dennis Schubert [:denschub]]

Release driver is bug 1950282, but let's run a full version bump to release without complicated single-uplifts.

Comment 1

[Dennis Schubert [:denschub]]

GitHub-mirror is updated, build tooling is updated, too. I just created a new xpi release on Ship-It, and scheduled a dep-sign build.

Comment 2

[Dennis Schubert [:denschub]]

Link to the dep-signed .xpi.

I have verified that .xpi using unbranded builds for 135 and 136, with only xpinstall.signatures.dev-root set to true. Installing the update works as expected, the update persists through reboots, about:compat loads and lists f1tv.formula1.com, and the browser block message on that site is gone. I spot-checked a few other interventions, they also pass.

So this is my sign-off that the dep-signed .xpi works. I'll have Tom confirm that, too, just so we don't have a "works on my machine" problem.

Comment 3

[Thomas Wisniewski [:twisniewski]]

I just confirmed both on my macbook as well.

Comment 4

[Dennis Schubert [:denschub]]

The update is signed and live on the release-sysaddon staging channel with a balrog role targetting 136.0.

Comment 5

[Dennis Schubert [:denschub]]

Hey Raul - as warned, I have some Addon QA work for you!

Using the 136.0 release builds (download links in case the update is not live yet: Windows, macOS, Linux)

1. In a fresh profile, confirm that on about:support, in the Firefox Features section, it shows Web Compatibility Interventions with the current version, 136.7.0.
2. Go to https://f1tv.formula1.com and verify that you see the "unsupported browser" banner.
3. Open about:config, edit extensions.systemAddon.update.url, and set it to https://aus5.mozilla.org/update/3/SystemAddons/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/release-sysaddon/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
4. Open the Firefox DevTools. In the DevTools, open the Settings via the Three-Dot-Menu -> Settings. In there, enable the checkbox Enable browser chrome and add-on debugging toolboxes.
5. Open the Firefox Browser Console:
   • on Linux and Windows, press Ctrl+Shift+J to open it
   • on macOS, it's Cmd+Shift+J
6. In that new console, run ChromeUtils.importESModule("resource://gre/modules/AddonManager.sys.mjs", { global: "shared" }).AddonManagerPrivate.backgroundUpdateCheck();
7. You won't see any progress, the update happens in the background. Wait 30 seconds, just to make sure Firefox has enough time to download and apply all updates.
8. Head back to about:support, and confirm that the Interventions version number now shows 137.5.20250303.181531
9. Check that about:compat loads and shows a list of active interventions.
10. Verify that the "unsupported browser" banner on https://f1tv.formula1.com is no longer there.
11. Restart Firefox, keeping the same profile. Verify that the version number in about:support is still 137.5.20250303.181531, and that the unsupported banner on f1tv is still gone.

If everything works as expected on Windows, macOS, and Linux, please leave a comment here saying as much. Thank you so much!

Comment 6

[Raul Bucata]

Following the steps provided, everything works as expected: the unsupported banner is no longer present

Tested with:

Browser / Version: Firefox Release 136.0 (64-bit)
Operating System: Windows 10 PRO x64
Operating System: Ubuntu 22.4 LTS x64
Operating System: Mac Ventura 13.1

Comment 7

[Dennis Schubert [:denschub]]

The OOB update is now live for Desktop 136.0. Users of 136 will get the update delivered in the background, usually within 24 hours, but it can sometimes take longer, depending on the client. I have confirmed that a fresh 136 profile updated just fine.

I'll close this bug as fixed.