From e9b59a540ed5e360dbdbc018830daa828f9ec067 Mon Sep 17 00:00:00 2001
From: Mikhail Koliada <88318005+mikhailkoliada@users.noreply.github.com>
Date: Thu, 29 Dec 2022 15:28:19 +0100
Subject: [PATCH] Revert "[Ubuntu] hardcode chromium revision for 108.x
 (#6734)" (#6851)

This reverts commit fb484d95309e2fdb6b943ba345c0e0975de10e68.
---
 images/linux/scripts/installers/google-chrome.sh | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/images/linux/scripts/installers/google-chrome.sh b/images/linux/scripts/installers/google-chrome.sh
index cc33261f5..5a6ca806b 100644
--- a/images/linux/scripts/installers/google-chrome.sh
+++ b/images/linux/scripts/installers/google-chrome.sh
@@ -14,13 +14,6 @@ function GetChromiumRevision {
     URL="https://omahaproxy.appspot.com/deps.json?version=${CHROME_VERSION}"
     REVISION=$(curl -s $URL | jq -r '.chromium_base_position')
 
-    # both 108.0.5359.98 and 108.0.5359.94 return old incorrect revision
-    # nothing to compare with, hardcode temporarily.
-    # see https://github.com/actions/runner-images/issues/6723
-    if [ $REVISION -eq "1016" ]; then
-       REVISION="1054926"
-    fi
-
     # Some Google Chrome versions are based on Chromium revisions for which a (usually very old) Chromium release with the same number exist. So far this has heppened with 4 digits long Chromium revisions (1060, 1086).
     # Use the previous Chromium release when this happens to avoid downloading and installing very old Chromium releases that would break image build because of incompatibilities.
     # First reported with: https://github.com/actions/runner-images/issues/5256