From b253509c8b82cad8ff8fc10d3818f47f0a91f6df Mon Sep 17 00:00:00 2001
From: Mikhail Koliada <88318005+mikhailkoliada@users.noreply.github.com>
Date: Wed, 8 Mar 2023 10:53:16 +0100
Subject: [PATCH] Revert "[Ubuntu] hardcode chromium revision for 110.x
 (#7113)" (#7248)

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

diff --git a/images/linux/scripts/installers/google-chrome.sh b/images/linux/scripts/installers/google-chrome.sh
index d541ab005..5a6ca806b 100644
--- a/images/linux/scripts/installers/google-chrome.sh
+++ b/images/linux/scripts/installers/google-chrome.sh
@@ -14,12 +14,6 @@ function GetChromiumRevision {
     URL="https://omahaproxy.appspot.com/deps.json?version=${CHROME_VERSION}"
     REVISION=$(curl -s $URL | jq -r '.chromium_base_position')
 
-    # both 110.0.5481.100 and 110.0.5481.96 return old incorrect revision
-    # nothing to compare with, hardcode temporarily.
-    if [ $REVISION -eq "839" ]; then
-       REVISION="1084008"
-    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