Bug 41277: Prepare Tor Browser release 14.0.1

Related Issues

• #41277 (closed) #41289 (closed) (to foreport then) #41282 (closed)

Self-review + reviewer's template

- [ ] `rbm.conf` updates:
  - [ ] `var/torbrowser_version`
  - [ ] `var/torbrowser_build`: should be `build1`, unless bumping a previous release preparation
  - [ ] `var/browser_release_date`: must not be in the future when we start building
  - [ ] `var/torbrowser_incremental_from` (not needed for Android-only releases)
- [ ] Tag updates:
  - [ ] [Firefox](https://gitlab.torproject.org/tpo/applications/tor-browser/-/tags)
  - [ ] Geckoview - should match Firefox
  - [ ] [Firefox Android](https://gitlab.torproject.org/tpo/applications/firefox-android/-/tags)
  - Tags might be speculative in the release preparation: i.e., they might not exist yet.
- [ ] Addon updates:
  - [ ] [NoScript](https://addons.mozilla.org/en-US/firefox/addon/noscript/)
  - [ ] [uBlock Origin](https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/) (Mullvad Browser only)
  - [ ] [Mullvad Browser Extension](https://github.com/mullvad/browser-extension/releases) (Mullvad Browser only)
  - For AMO extension (NoScript and uBlock), updating the version in the URL is not enough, check that also a numeric ID from the URL has changed
- [ ] Tor and dependencies updates (Tor Browser only)
  - [ ] [Tor](https://gitlab.torproject.org/tpo/core/tor/-/tags)
  - [ ] [OpenSSL](https://www.openssl.org/source/): we stay on the latest LTS channel (currently 3.0.x)
  - [ ] [zlib](https://github.com/madler/zlib/releases)
  - [ ] [Zstandard](https://github.com/facebook/zstd/releases) (Android only, at least for now)
  - [ ] [Go](https://go.dev/dl): avoid major updates, unless planned
- [ ] Manual version update (Tor Browser only, optional)
- [ ] Changelogs
  - [ ] Changelogs must be in sync between stable and alpha
  - [ ] Check the browser name
  - [ ] Check the version
  - [ ] Check the release date
  - [ ] Check we include only the platform we're releasing for (e.g., no Android in desktop-only releases)
  - [ ] Check all the updates from above are reported in the changelogs
  - [ ] Check for major errors
    - If you find errors such as platform or category (build system) please adjust the issue label accordingly
    - You can run `tools/relprep.py --only-changelogs --date $date $version` to update only the changelogs

Review

Request Reviewer

• Request review from a release engineer: boklm, dan, ma1, morgan, pierov

@boklm can you check if I've done things correctly for the legacy channel?

Change Description

requested review from @boklm

assigned to @pierov

Self review

• rbm.conf updates:
  • var/torbrowser_version
  • var/torbrowser_build: should be build1, unless bumping a previous release preparation
  • var/browser_release_date: must not be in the future when we start building
  • var/torbrowser_incremental_from (not needed for Android-only releases)
• Tag updates:
  • Firefox
  • Geckoview - should match Firefox
  • Tags might be speculative in the release preparation: i.e., they might not exist yet.
• Addon updates:
  • NoScript
  • uBlock Origin (Mullvad Browser only) (no MB)
  • Mullvad Browser Extension (Mullvad Browser only) (no MB)
  • For AMO extension (NoScript and uBlock), updating the version in the URL is not enough, check that also a numeric ID from the URL has changed
• Tor and dependencies updates (Tor Browser only) - only Tor
  • Tor
  • OpenSSL: we stay on the latest LTS channel (currently 3.0.x)
  • zlib
  • Zstandard (Android only, at least for now)
  • Go: avoid major updates, unless planned
• Manual version update (Tor Browser only, optional)
• Changelogs
  • Changelogs must be in sync between stable and alpha We won't sync changelogs anymore
  • Check the browser name
  • Check the version
  • Check the release date
  • Check we include only the platform we're releasing for (e.g., no Android in desktop-only releases)
  • Check all the updates from above are reported in the changelogs
  • Check for major errors
    • If you find errors such as platform or category (build system) please adjust the issue label accordingly
    • You can run tools/relprep.py --only-changelogs --date $date $version to update only the changelogs

@boklm can you check if I've done things correctly for the legacy channel?

Yes, lgtm.

approved this merge request

• rbm.conf updates:
  • var/torbrowser_version
  • var/torbrowser_build: should be build1, unless bumping a previous release preparation
  • var/browser_release_date: must not be in the future when we start building
  • var/torbrowser_incremental_from (not needed for Android-only releases)
• Tag updates:
  • Firefox
  • Geckoview - should match Firefox
  • Firefox Android
  • Tags might be speculative in the release preparation: i.e., they might not exist yet.
• Addon updates:
  • NoScript
  • uBlock Origin (Mullvad Browser only) (no MB)
  • Mullvad Browser Extension (Mullvad Browser only) (no MB)
  • For AMO extension (NoScript and uBlock), updating the version in the URL is not enough, check that also a numeric ID from the URL has changed
• Tor and dependencies updates (Tor Browser only)
  • Tor
  • OpenSSL: we stay on the latest LTS channel (currently 3.0.x)
  • zlib
  • Zstandard (Android only, at least for now)
  • Go: avoid major updates, unless planned
• Manual version update (Tor Browser only, optional)
• Changelogs
  • Changelogs must be in sync between stable and alpha
  • Check the browser name
  • Check the version
  • Check the release date
  • Check we include only the platform we're releasing for (e.g., no Android in desktop-only releases)
  • Check all the updates from above are reported in the changelogs
  • Check for major errors
    • If you find errors such as platform or category (build system) please adjust the issue label accordingly
    • You can run tools/relprep.py --only-changelogs --date $date $version to update only the changelogs

added 2 commits

• 0d408746 - fixup! Bug 41277: Prepare Tor Browser release 14.0.1.
• e0f09ec8 - fixup! Bug 41277: Prepare Tor Browser release 14.0.1.

Compare with previous version

marked this merge request as draft from pierov/tor-browser-build@0d408746

resolved all threads

added 1 commit

• f076e0b0 - Bug 41277: Prepare Tor Browser release 14.0.1.

Compare with previous version

Oops, it seems I had forgotten to push the changelog amend for the Python downgrade initially.

marked this merge request as ready

merged