From 5f256d118fa289412c95562f91cd5d76a20ba4d1 Mon Sep 17 00:00:00 2001
From: Mira Ressel <mira@parity.io>
Date: Tue, 9 May 2023 17:33:48 +0200
Subject: [PATCH] Move back to ci-linux:production image after upgrade (#7207)

There are still a bunch of open questions on how to handle image
pinning; in the meantime, let's keep using the production tag.
---
 polkadot/.gitlab-ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/polkadot/.gitlab-ci.yml b/polkadot/.gitlab-ci.yml
index 29c05855b0..01e47746b5 100644
--- a/polkadot/.gitlab-ci.yml
+++ b/polkadot/.gitlab-ci.yml
@@ -33,7 +33,7 @@ variables:
   GIT_STRATEGY: fetch
   GIT_DEPTH: 100
   CI_SERVER_NAME: "GitLab CI"
-  CI_IMAGE: "paritytech/ci-linux@sha256:f6cdc1e289e40f3eb1f93efb11f961d4f0e51f4c2adf80b31300ab5b35ef1386" # staging 2023-05-02
+  CI_IMAGE: "paritytech/ci-linux:production"
   BUILDAH_IMAGE: "quay.io/buildah/stable:v1.29"
   BUILDAH_COMMAND: "buildah --storage-driver overlay2"
   DOCKER_OS: "debian:stretch"