From 0c091c6de3ce364977ea44fa58556318c920116f Mon Sep 17 00:00:00 2001
From: Mark007-R <markrodrigues2004@gmail.com>
Date: Sun, 24 May 2026 13:19:47 +0530
Subject: [PATCH] =?UTF-8?q?sprint:=20relax=20protobuf=20pin=20from=20=3D?=
 =?UTF-8?q?=3D5.24.1=20(yanked=20from=20PyPI)=20to=20>=3D4.25,<6=20(Day=20?=
 =?UTF-8?q?7=20CI=20fix)=20=E2=80=94=20fresh=20installs=20were=20failing?=
 =?UTF-8?q?=20on=20'No=20matching=20distribution=20found=20for=20protobuf?=
 =?UTF-8?q?=3D=3D5.24.1';=20resolver=20now=20picks=204.25.9=20which=20stre?=
 =?UTF-8?q?amlit=201.28.1=20accepts?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 requirements.txt | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/requirements.txt b/requirements.txt
index 5d45ba0..6bd1803 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -14,7 +14,12 @@ jupyter==1.0.0
 streamlit==1.28.1
 plotly==5.18.0
 altair==5.1.2
-protobuf==5.24.1
+# protobuf: was pinned to ==5.24.1, which PyPI later yanked. The 5.24.x and
+# 5.25.x lines are unreachable on a fresh install; available 5.x runs jump
+# from 5.23.4 to 5.26.0. Relax to a range so pip's resolver picks whatever
+# streamlit / mlflow / plotly mutually agree on. Day-7 CI exposed this on
+# the first clean install.
+protobuf>=4.25,<6
 
 # Day 1 -- MLflow tracking + registry (sqlite-backed locally)
 mlflow>=2.18,<3