Bug 41688: Rebased stable to 102.10 ESR (!608) · Merge requests · The Tor Project / Applications / Tor Browser

Merge Info

Immediate - patchsets for critical bug fixes or other major blocker (e.g. fixes for a 0-day exploit) OR patchsets with trivial changes which do not need testing (e.g. fixes for typos or fixes easily verified in a local developer build)
Next Minor Stable Release - patchset that needs to be verified in nightly before backport
Eventually - patchset that needs to be verified in alpha before backport
No Backport - patchset for the next major stable

Merge to base-browser - typically for !fixups to patches in the base-browser branch, though sometimes new patches as well
- NOTE: if your changeset includes patches to both base-browser and tor-browser please please make separate merge requests for each part

Link resolved issues with appropriate Release Prep issue for changelog generation

Range-diff before squash was clean (no change at all).

Diff of diff after squash was clean, too.

No fixups have been added (yet) even though we have a couple of open issues.

I'd say no MR for base-browser, and we could just fast-forward the branch once it's merged.