fix(workflow): use --no-build on uv tool install harbor

Previous fix used an inline # nosonar suppression based on the wrong
assumption that uv tool install has no --no-build equivalent. uv DOES
accept --no-build on  (verified via 'uv tool install
--help' and a smoke-test install). This removes the nosonar hack and
uses the real flag, so the SonarCloud S2648 rule is satisfied at the
source rather than suppressed.

Co-Authored-By: Claude <[email protected]>
This commit is contained in:
Claude
2026-08-11 23:52:54 -04:00
parent 78c59e7ac2
commit 0c9236b84a
+4 -5
View File
@@ -43,11 +43,10 @@ jobs:
run: "pip install uv==0.5.9 --only-binary :all:"
- name: Install Harbor
# harbor 0.21.0 ships as a pure-Python wheel on PyPI; no source build,
# so no setup.py ever runs. Pin is exact. uv has no --no-build
# equivalent for `uv tool install`; suppress the S2648 warning
# locally with # nosonar.
run: "uv tool install harbor==0.21.0" # nosonar — see comment above
# --no-build prevents uv from building source distributions if no
# wheel is available. harbor 0.21.0 ships as a wheel on PyPI;
# --no-build is the belt-and-suspenders safeguard.
run: "uv tool install harbor==0.21.0 --no-build"
- name: Docker info (fail-fast if missing)
run: docker info