From 2197b05d6c6692d402a0b687b5aa8a177ce7d0ed Mon Sep 17 00:00:00 2001
From: prql-bot <107324867+prql-bot@users.noreply.github.com>
Date: Sun, 23 Aug 2026 19:25:24 +0000
Subject: [PATCH 1/2] ci: pin the mssql test container to the 2022 line

---
 prqlc/prqlc/tests/integration/dbs/docker-compose.yaml | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/prqlc/prqlc/tests/integration/dbs/docker-compose.yaml b/prqlc/prqlc/tests/integration/dbs/docker-compose.yaml
index d2863b1029f0..ed41a2b3746c 100644
--- a/prqlc/prqlc/tests/integration/dbs/docker-compose.yaml
+++ b/prqlc/prqlc/tests/integration/dbs/docker-compose.yaml
@@ -21,7 +21,16 @@ services:
     command: --secure-file-priv=""
     volumes: *vol
   mssql:
-    image: "mcr.microsoft.com/mssql/server"
+    # Pinned to the 2022 line: the untagged image resolves to `latest`, which is
+    # now SQL Server 2025, and that crashes in SQLPAL on startup depending on
+    # the host it lands on — intermittently red CI, with the container gone
+    # before the port ever opens. Upstream reports 2025 crashing where
+    # `2022-latest` is fine on the same host:
+    # https://github.com/microsoft/mssql-docker/issues/954
+    # https://github.com/microsoft/mssql-docker/issues/940
+    # `2022-latest` still floats within the 2022 line, so cumulative updates
+    # arrive without another silent major-version jump.
+    image: "mcr.microsoft.com/mssql/server:2022-latest"
     ports:
       - "1433:1433"
     # https://github.com/microsoft/mssql-docker/issues/668#issuecomment-1436802153

From 3b0fe25957e99c0d0428fb8e55d50abde1b45040 Mon Sep 17 00:00:00 2001
From: prql-bot <107324867+prql-bot@users.noreply.github.com>
Date: Sun, 23 Aug 2026 19:34:09 +0000
Subject: [PATCH 2/2] ci: point the mssql comment at the open upstream issue

microsoft/mssql-docker#954 is closed as a duplicate of #951, which is the
open tracking issue for the SQLPAL startup assertion. Point the comment at
the live thread so a reader doesn't take "closed" for "fixed".
---
 prqlc/prqlc/tests/integration/dbs/docker-compose.yaml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/prqlc/prqlc/tests/integration/dbs/docker-compose.yaml b/prqlc/prqlc/tests/integration/dbs/docker-compose.yaml
index ed41a2b3746c..f8c35c8c566a 100644
--- a/prqlc/prqlc/tests/integration/dbs/docker-compose.yaml
+++ b/prqlc/prqlc/tests/integration/dbs/docker-compose.yaml
@@ -26,7 +26,8 @@ services:
     # the host it lands on — intermittently red CI, with the container gone
     # before the port ever opens. Upstream reports 2025 crashing where
     # `2022-latest` is fine on the same host:
-    # https://github.com/microsoft/mssql-docker/issues/954
+    # https://github.com/microsoft/mssql-docker/issues/951 (the open tracking
+    # issue; #954 was closed as a duplicate of it)
     # https://github.com/microsoft/mssql-docker/issues/940
     # `2022-latest` still floats within the 2022 line, so cumulative updates
     # arrive without another silent major-version jump.