Release: fix build inside Fedora
What changed, and why it matters
This commit fixes a build script used to create official releases inside a Fedora Docker container. It adds one command to create a Python virtual environment before installing dependencies. There is no security issue here—it's a routine build-fix.
No security action needed. Treat as a normal build/maintenance fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change is in tools/build-release.sh. When the script runs with –inside-docker, it now runs uv venv before uv export and uv pip install. This resolves the error ‘No virtual environment found for Python 3.12’ that occurs when uv tries to install packages without an active venv. The patch is purely a build-environment fix.
Changed components
tools/build-release.shInspect captured patch +1 / −0
diff --git a/tools/build-release.sh b/tools/build-release.sh
index 3b65ac1d..b52a3362 100755
--- a/tools/build-release.sh
+++ b/tools/build-release.sh
@@ -11,6 +11,7 @@ if [ "$1" = "--inside-docker" ]; then
git config --global --add safe.directory /src/.git
git clone /src /build
cd /build || exit
+ uv venv
uv export --format requirements.txt > /tmp/requirements.txt
uv pip install -r /tmp/requirements.txt
./configure
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.