setup-chrome icon indicating copy to clipboard operation
setup-chrome copied to clipboard

Need help on finding revision / commit number

Open krisanalfa opened this issue 2 years ago • 7 comments

Hi, first of all thank you for your hard work making this possible. I hope I can help you on that "download with exact chromium version". Because that's exactly my problem now. I want to download Chromium with exact version => 97.0.4692.115. How can I get the commit number?

Here's the tag I got from the git repo => https://chromium.googlesource.com/chromium/src/+/refs/tags/97.0.4692.115

krisanalfa avatar Apr 05 '22 02:04 krisanalfa

Also would like to know this, I can't find this info anywhere

owens-ben avatar May 04 '22 16:05 owens-ben

I found this list of all old stable versions of Chromium , which may help. The value you want is download position, which you can verify by reading the source for snapshot.ts and looking at how it constructs URLs.

I'm able to install a selected version with these version numbers, but I'm still having problems with #240 in trying to actually run it.

eToThePiIPower avatar Jun 24 '22 03:06 eToThePiIPower

This had me stumped as well – it's really difficult to match an actual Chromium version to the "commit position" described in the README.

But I think I finally found a method that works:

  1. Go to https://chromium.googlesource.com/chromium/src/+refs
  2. Click on the link for the version you want, eg for 107.0.5304.9, you'll link to https://chromium.googlesource.com/chromium/src/+/refs/tags/107.0.5304.9
  3. Click on the parent link, which in the example above links to https://chromium.googlesource.com/chromium/src/+/b36b08f306ee7dc7689f992837e0c06b651c935d
  4. Look for refs/heads/main@{#, and copy the number after that: 1047731

Screenshot 2022-10-26 at 17 55 23

That is the value to use for chrome-version:

      - name: Download Chrome
        uses: browser-actions/setup-chrome@latest
        with:
          chrome-version: 1047731

mcalthrop avatar Oct 26 '22 16:10 mcalthrop

@ueokande ☝️ FYI

mcalthrop avatar Oct 26 '22 17:10 mcalthrop

FWIW, I ended up downloading Chrome directly from within the GitHub workflow like this:

sudo apt-get update
sudo apt-get install --yes \
  fonts-liberation \
  libcairo2 \
  libgbm1 \
  libgtk-3-0 \
  libpango-1.0-0 \
  libxdamage1 \
  libxkbcommon0 \
  xdg-utils \
  libu2f-udev
CHROME_DOWNLOAD=google-chrome-stable_current_amd64.deb
curl --no-progress-meter \
  --output /tmp/${CHROME_DOWNLOAD} \
  https://dl.google.com/linux/direct/${CHROME_DOWNLOAD}
apt install --yes /tmp/${CHROME_DOWNLOAD}

Unfortunately using the Action in this repo is too brittle.

mcalthrop avatar Oct 27 '22 09:10 mcalthrop

@mcalthrop - Thanks for dropping the instructions above, fixed my issue. Was bemused to realize that chrome-version needs to be a commit position and not a semver version (Of course I shouldn't complain about free and open source actions! :P)

patti-c avatar Mar 28 '23 17:03 patti-c

I found this list of all old stable versions of Chromium , which may help. The value you want is download position, which you can verify by reading the source for snapshot.ts and looking at how it constructs URLs.

I'm able to install a selected version with these version numbers, but I'm still having problems with #240 in trying to actually run it.

This was the key for me, thank you. The number needed is the download position, which can be very easily looked up for the desired version using that link. I tried several times with mcalthrop's solution but couldn't get it working - the number it was giving me was very close but wasn't the one I needed - 1135570 instead of 1135561 - and kept resulting in 404s.

hashimaziz1 avatar Aug 27 '23 22:08 hashimaziz1

The setup-chrome action now supports two type of exact versions; the four-parts of version and commit position

  • Specific versions: 119, 120.0.6099, 121.0.6100.0. The version are resolved by Chrome for Testing.
  • Commit positions like 1295939. You can find commit positions from here.

Thank you for your request, and I'm closing this issue.

ueokande avatar May 03 '24 14:05 ueokande