fix: constrain conan version to 2.x in release-builder

Prevent potential breakage from future Conan 3.x by explicitly
constraining pip install to "conan>=2.0,<3.0"
This commit is contained in:
Nicholas Dudfield
2025-10-06 14:17:50 +07:00
parent 03cec6cb4f
commit a6377be629

View File

@@ -93,7 +93,7 @@ RUN /hbb_exe/activate-exec bash -c "dnf install -y epel-release && \
dnf clean all" dnf clean all"
# Install Conan 2 and CMake # Install Conan 2 and CMake
RUN /hbb_exe/activate-exec pip3 install "conan>=2.0" && \ RUN /hbb_exe/activate-exec pip3 install "conan>=2.0,<3.0" && \
/hbb_exe/activate-exec wget -q https://github.com/Kitware/CMake/releases/download/v3.23.1/cmake-3.23.1-linux-x86_64.tar.gz -O cmake.tar.gz && \ /hbb_exe/activate-exec wget -q https://github.com/Kitware/CMake/releases/download/v3.23.1/cmake-3.23.1-linux-x86_64.tar.gz -O cmake.tar.gz && \
mkdir cmake && \ mkdir cmake && \
tar -xzf cmake.tar.gz --strip-components=1 -C cmake && \ tar -xzf cmake.tar.gz --strip-components=1 -C cmake && \