Mixed content of Google Chrome and Chromium

[woolyss]

Hello Cypress,

Note that your tool mixes Google Chrome and Chromium content.
So your tool is corrupted! :/

The Google Chrome development is different than the Chromium development.

• Google Chrome is closed-source
• Chromium is open-source

In your source code:
https://github.com/cypress-io/chromium-downloads/blob/master/backend/get-chromium-builds/index.js

OmahaProxy

As you see, your tool is based on OmahaProxy.

OmahaProxy is a tool to follow the different steps of the Google Chrome development:

• https://omahaproxy.appspot.com/ (My screenshot)
• https://chromium.googlesource.com/chromium/chromium/+/trunk/tools/omahaproxy.py
• https://developer.chrome.com/apps/faq (search the "OmahaProxy" word)

Finally, I found an image on the Web to explain that easily! (source)

Chromium !== Google Chrome

For example, Chromium has many versions each day.
The DEV version of Google Chrome is released every 1-2 week.
The CANARY version of Google Chrome is released each day.

For example, the versions of Google Chrome are patched (My screenshot)
The binaries of Chromium (shared by the Chromium team) are never patched.
https://www.chromium.org/developers/version-numbers

chromium-browser-snapshots

chromium-browser-snapshots is the official root directory of all Chromium binaries released automatically by the buildbot (= shared by the Chromium team, aka "The Chromium Authors") .

Chromium is still in development. There are no "official chromium", no "stable chromium", no "beta chromium" shared by the Chromium team.
If you want to release a STABLE (or BETA...) version of Chromium, you must to re-compile it yourself. That is why you can find different Chromium releases for Windows, Mac, Linux, Bsd and Android at https://chromium.woolyss.com/

Conclusion

So you must to rewrite your tool to share corrected info and releases about Chromium.
Forget the OmahaProxy tool.

Good luck!

Regards,

Jerry

[flotwig]

Hey @woolyss, thanks for explaining all of this so clearly. It seems like this is the best fix:

• Remove the notion of "channels" from chromium-downloads - that's a Chrome notion, all of these builds are Developer builds
• Instead of using omaha-proxy to guess the version based off Chrome (error-prone), download the binary itself from the artifact server and pull the version off --version output

Does that sound right?

[woolyss]

Hi @flotwig

1. Right. Do not use these channels. Chromium is only in development (=only developer builds).

2. Right. Exactly. Read the Chromium version of the manifest file (in the ZIP archive).
   Example with the revision 710903:
   Download the "chrome-win.zip" from this chromium-browser-snapshots...Win_x64/710903
   Unzip it. You will see the version in the manifest file.

[jennifer-shehane]

We intend to no longer maintain this service, so we're closing this.

We recommend using an alternative for downloading Chromium like: https://vikyd.github.io/download-chromium-history-version