Repository navigation
ci: Lock uv version for renovate bot - #3701
Conversation
Signed-off-by: Zakharov, Ivan <ivan.zakharov@intel.com>
There was a problem hiding this comment.
Pull request overview
This PR standardizes the uv version used across CI and Renovate to reduce uv.lock regeneration drift (related to #3666), and makes the Windows Tauri sidecar build use a frozen environment resolution.
Changes:
- Pin
uvto0.9.18in thetauri-buildworkflow and switchuv syncto--frozenfor deterministic installs. - Configure Renovate to (a) not recreate closed PRs and (b) constrain the
uvtool version to0.9.18when regeneratinguv.lock.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/tauri-build.yaml |
Pins uv and makes uv sync deterministic via --frozen during Windows sidecar builds. |
.github/renovate.json5 |
Pins Renovate’s uv tool via constraints and disables recreation of closed PRs. |
Docker Image SizesCPU
CUDA
XPU
|
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Ivan Zakharov <ivan.zakharov@intel.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (2)
.github/renovate.json5:60
recreateWhen: "never"changes Renovate behavior globally (including potentially lockfile-maintenance PR recreation) but isn’t mentioned in the PR description/title about pinninguv. If this isn’t intentionally part of the uv-version fix, it should be removed (or moved to a separate PR) to avoid unexpectedly suppressing dependency update PRs.
// Do not recreate PRs that were closed without merging.
// Note: security/vulnerability ("immortal") updates may still be recreated.
recreateWhen: "never",
.github/workflows/tauri-build.yaml:267
- To keep the workflow aligned with
anomalib-studio.yamland fail fast with a clearer error when the lockfile is out of date, consider runninguv lock --checkbeforeuv sync --frozen. (--frozenwill fail too, butuv lock --checkmakes the intent explicit and matches the other workflow’s pattern.)
run: |
uv sync --frozen --no-dev --extra $env:MATRIX_ACCELERATOR
uv pip install pyinstaller==6.19.0
AlexanderBarabanov
left a comment
There was a problem hiding this comment.
Thank you for looking into this!
I do not think this will fully resolve our issue, as it appears the root cause is the version of uv used by Renovate.
Could you please help verify the expected behavior by following these steps?
- Generate
application/backend/uv.locklocally using uv0.9.18, then scan the file with Trivy. - Generate
application/backend/uv.locklocally using uv0.11.28, then scan the file with Trivy. - Compare the two reports.
Expected results: neither Trivy report should contain CVE-2025-3730 or CVE-2025-2953.
My expectation is that report 1 (generated with 0.9.18) will include these CVEs, while report 2 (generated with 0.11.28) will not - which would indicate that we need to upgrade the uv version being used.
|
I've got same uv.lock file (no changes) with both uv versions, and as result trivy has produced same report with 2 LOW-severity findings in torch 2.9.1+xpu (CVE-2025-3000, CVE-2025-3001), no MEDIUM/HIGH/CRITICAL |
|
It did not help, after merging this PR Renovate use |
📝 Description
Locking uv tool version for renovate bot, it is aligned to what is used in anomalib-studio workflow. Same is doen for tauri-build workflow.
✨ Changes
Select what type of change your PR is:
✅ Checklist
Before you submit your pull request, please make sure you have completed the following steps:
For more information about code review checklists, see the Code Review Checklist.