Skip to content

ci: Lock uv version for renovate bot - #3701

Merged
AlexanderBarabanov merged 2 commits into
mainfrom
ivanzati/renovate-uv-version-lock
Jul 30, 2026
Merged

AlexanderBarabanov merged 2 commits into
mainfrom
ivanzati/renovate-uv-version-lock

Conversation

@ivanzati

Copy link
Copy Markdown
Contributor

📝 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:

  • 🚀 New feature (non-breaking change which adds functionality)
  • 🐞 Bug fix (non-breaking change which fixes an issue)
  • 🔄 Refactor (non-breaking change which refactors the code base)
  • ⚡ Performance improvements
  • 🎨 Style changes (code style/formatting)
  • 🧪 Tests (adding/modifying tests)
  • 📚 Documentation update
  • 📦 Build system changes
  • 🚧 CI/CD configuration
  • 🔧 Chore (general maintenance)
  • 🔒 Security update
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)

✅ Checklist

Before you submit your pull request, please make sure you have completed the following steps:

  • 📚 I have made the necessary updates to the documentation (if applicable).
  • 🧪 I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).
  • 🏷️ My PR title follows conventional commit format.

For more information about code review checklists, see the Code Review Checklist.

Signed-off-by: Zakharov, Ivan <ivan.zakharov@intel.com>
Copilot AI review requested due to automatic review settings July 28, 2026 10:40
@ivanzati
ivanzati requested a review from a team as a code owner July 28, 2026 10:40
@ivanzati
ivanzati temporarily deployed to windows-msix-signing July 28, 2026 10:40 — with GitHub Actions Inactive
@ivanzati
ivanzati had a problem deploying to windows-msix-signing July 28, 2026 10:40 — with GitHub Actions Error
@ivanzati
ivanzati had a problem deploying to windows-msix-signing July 28, 2026 10:40 — with GitHub Actions Error

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 uv to 0.9.18 in the tauri-build workflow and switch uv sync to --frozen for deterministic installs.
  • Configure Renovate to (a) not recreate closed PRs and (b) constrain the uv tool version to 0.9.18 when regenerating uv.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.

Comment thread .github/renovate.json5 Resolved
@github-actions

github-actions Bot commented Jul 28, 2026 •

Copy link
Copy Markdown

Docker Image Sizes

CPU

Image Size
anomalib-studio-cpu:pr-3701 978.89M
anomalib-studio-cpu:sha-53d2be8 978.89M

CUDA

Image Size
anomalib-studio-cuda:pr-3701 4.35G
anomalib-studio-cuda:sha-53d2be8 4.35G

XPU

Image Size
anomalib-studio-xpu:pr-3701 3.02G
anomalib-studio-xpu:sha-53d2be8 3.02G

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Ivan Zakharov <ivan.zakharov@intel.com>
Copilot AI review requested due to automatic review settings July 28, 2026 10:57
@ivanzati
ivanzati temporarily deployed to windows-msix-signing July 28, 2026 10:58 — with GitHub Actions Inactive
@ivanzati
ivanzati temporarily deployed to windows-msix-signing July 28, 2026 10:58 — with GitHub Actions Inactive
@ivanzati
ivanzati temporarily deployed to windows-msix-signing July 28, 2026 10:58 — with GitHub Actions Inactive

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 pinning uv. 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.yaml and fail fast with a clearer error when the lockfile is out of date, consider running uv lock --check before uv sync --frozen. (--frozen will fail too, but uv lock --check makes 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

@ivanzati
ivanzati requested a review from ashwinvaidya17 July 28, 2026 11:17

@AlexanderBarabanov AlexanderBarabanov left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

  1. Generate application/backend/uv.lock locally using uv 0.9.18, then scan the file with Trivy.
  2. Generate application/backend/uv.lock locally using uv 0.11.28, then scan the file with Trivy.
  3. 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.

@ivanzati

Copy link
Copy Markdown
Contributor Author

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

@AlexanderBarabanov
AlexanderBarabanov merged commit 5ba0564 into main Jul 30, 2026
49 checks passed
@AlexanderBarabanov
AlexanderBarabanov deleted the ivanzati/renovate-uv-version-lock branch July 30, 2026 07:31
@AlexanderBarabanov

Copy link
Copy Markdown
Contributor

It did not help, after merging this PR Renovate use 0.9.18 but PR still contain lock file with CVE-2025-3730 or CVE-2025-2953 (log)

This branch was previously deployed

1 inactive deployment
windows-msix-signing — 790e46b7 Deployed Jul 28, 2026 by ivanzati via Build Windows MSIX (cu130) #799
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Investigate why Dependabot re-opened some alerts

3 participants