Create Release Prep MR generating script

marked this issue as related to #41000

added Build System label

added 13.0 stable 13.5 stable All Platforms Backport Next labels

removed 13.0 stable 13.5 stable All Platforms Backport Next labels

added 13.0 stable 13.5 stable All Platforms Backport Next labels

removed 13.0 stable 13.5 stable All Platforms Backport Next labels

added Task label

added Next label

assigned to @richard

added 13.5 stable label

added Doing label and removed Next label

translation hash updates

This is easy!

from pathlib import Path

from git import Repo
import ruamel.yaml

yaml = ruamel.yaml.YAML()
yaml.indent(mapping=2, sequence=4, offset=2)
yaml.width = 4096
yaml.preserve_quotes = True

tr_config = Path("projects/translation/config")
tr_repo = Repo("git_clones/translation")
tr_repo.remote("origin").fetch()
tr = yaml.load(tr_config)
for i in ["base-browser", "tor-browser", "mullvad-browser", "fenix"]:
    branch = tr["steps"][i]["targets"]["nightly"]["git_hash"] 
    tr["steps"][i]["git_hash"] = str(tr_repo.rev_parse("origin/" + branch))
with tr_config.open("w") as f:
    yaml.dump(tr, f)

dependency checking and config updating for:

noscript

ublock

We update the allowed-addons.json for Android. This file happened to have URLs and sha256 already.

Or, if we don't update it, we can use the same REST API used to generate it.

mullvad extension

openssl

zlib

These are all on GitHub.

Earlier, I've discovered that on GitHub you can add .atom at the end of the release page URL, and you'll get a machine readable version (Atom feeds).

The version is usually embedded somehow in the git tag, that we could get by parsing the release entry id (tag:github.com,2008:Repository/$repositoryId/$tag) or the link (https://github.com/$developer/$repo/releases/tag/$tag).

I think this should help with cases such as the withdrawn OpenSSL 1.1.1r (for which, if I understand correctly, the GitHub release was correctly deleted).

Also, we could add Zstd to the list (which is also on GitHub).

tor

git tag or https://gitlab.torproject.org/tpo/web/tpo/-/raw/main/databags/versions.ini.

go

https://go.dev/dl/?mode=json

But it's a little bit problematic at the moment, because of Windows (still, we could probably do it).

manual

Already automated .

Maybe we could make it even easier.

tor-browser

geckoview

git tag is probably the safest option here.

A problem might be that early alphas might not be based on an ESR, but it should be easy enough to solve (also, alphas are updated just after the rebase).

improved changelog generation (eg include esr/geckoview updates, etc)

Part of this has been done.

Room for improvement:

automatically sync the changelogs and write to the file without copying and pasting (it's possible to do some magic with GitPython, e.g., check if the last update was in maint-X or in main, or take the newest tag)
for each component, parse the YAML config at the previous release (which can be fetched with git show tag:projects/<project>/config), and check if var/version changed (or the addon URL, in case of NoScript and co.)
make it a function, so that we can run it from a relprep.py script ️

assigned to @pierov and unassigned @richard

marked the checklist item translation hash updates as completed

marked the checklist item noscript as completed

marked the checklist item ublock as completed

marked the checklist item mullvad extension as completed

marked the checklist item openssl as completed

marked the checklist item zlib as completed

marked the checklist item tor as completed

Create Release Prep MR generating script

Child items ...

Activity