No new mapping after 121.0.6158.0

[janbrasna]

Since the API endpoint used to get position data vikyd/chromium-history-version-crawler#3 stopped returning info, nothing new since is being crawled and processed.

Not sure there's another way to look into the deps files, but there are tickets around that the replacement dashboard https://chromiumdash.appspot.com doesn't have the same amount of various data available 🤷 but mainly I'm not sure their fetch data are to be consumed publicly etc. … There might be something in versionhistory.googleapis.com/v1/chrome but the more interesting results incl. positions are in https://chromiumdash.appspot.com/fetch_releases?channel=Stable&platform=Mac&num=6&offset=0 own jsons, so there's some git lookup in place to dig this kind of data. Chromium members have made various overview tools to compensate for the sunset of omahaproxy, with tables like https://web.evilbit.io/chrome.php or endpoints e.g. https://chromiumdash.appspot.com/fetch_version?version=110.0.5481.61 — can't tell if there's source code of that somewhere, to mimic the git operations, or a cached storage of the references to make use of…

So basically I gave in, and looked for more dumbed down approach, not interested in all the data but just "good" builds, those pushed to various release channels, and with that I've realised that there's cli tools that have to pull versions somehow so looked around puppeteer and found JSON endpoints publishing revisions for chrome-testing but that's enough for me to get the tuples mapping e.g. {"version":"123.0.6312.86","revision":"1262506"} for the most meaningful versions. The limitation here is that for headless testing it's covering only Linux builds IIRC, and only mapping "known good" build versions, but that's enough to get to some rather sane chromium snapshots;)