From f1abfa5fdef67ed2f06e93cea1fb01c0b44c1dcf Mon Sep 17 00:00:00 2001
From: Aleksandr Chebotov <47745270+al-cheb@users.noreply.github.com>
Date: Mon, 5 Sep 2022 12:54:06 +0200
Subject: [PATCH] Fix chromium revision parsing (#6182)

---
 images/linux/scripts/installers/google-chrome.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/images/linux/scripts/installers/google-chrome.sh b/images/linux/scripts/installers/google-chrome.sh
index 889690cd4..5a6ca806b 100644
--- a/images/linux/scripts/installers/google-chrome.sh
+++ b/images/linux/scripts/installers/google-chrome.sh
@@ -17,7 +17,7 @@ function GetChromiumRevision {
     # 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
-    if [ ${#REVISION} -eq 4 ]; then
+    if [ ${#REVISION} -le 4 ]; then
       CURRENT_REVISIONS=$(curl -s "https://omahaproxy.appspot.com/all.json?os=linux&channel=stable")
       PREVIOUS_VERSION=$(echo "$CURRENT_REVISIONS" | jq -r '.[].versions[].previous_version')
       URL="https://omahaproxy.appspot.com/deps.json?version=${PREVIOUS_VERSION}"