-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No more data from omahaproxy #3
Comments
Good idea, will be fixed in the next few days. |
Looking into it further, there a) seems to be an endpoint providing the data live https://chromiumdash.appspot.com/fetch_version?version=110.0.5481.61 (not sure how happy they'd be to have it called from outside or crawled thou;D) or b) there's a gh-pages "cached" built output of the mapping for chrome-for-testing json calls (can't tell if that one has saved all the versions or just known good, and a as a note contains only data starting w/ CfT so 112+…) |
Are you still intending to fix this? |
https://omahaproxy.appspot.com/
Announcement: https://groups.google.com/a/chromium.org/g/chromium-dev/c/uH-nFrOLWtE/m/PhUj_inyAQAJ
I'm looking into https://developer.chrome.com/blog/chrome-for-testing/ data and JSON endpoints for mapping milestone versions to revisions — and once you have a revision you can link to the chromium snapshots archive with it (instead of the chrome-testing endpoints it was designed for) so there might be viable alternatives.
The text was updated successfully, but these errors were encountered: