Repository navigation
ci: Exclude CVE-flagged torch 2.6.0+xpu from project toml - #3703
Merged
ivanzati merged 3 commits intoJul 31, 2026
Merged
Conversation
Signed-off-by: Zakharov, Ivan <ivan.zakharov@intel.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repository Renovate configuration to prevent closed uv.lock lockfile maintenance PRs from being automatically recreated, aligning Renovate behavior with the top-level recreateWhen: "never" intent.
Changes:
- Set
lockFileMaintenance.recreateWhen: "never"to stop Renovate from recreating closed lockfile-maintenance PRs. - Add inline documentation clarifying Renovate’s nested default behavior for
lockFileMaintenance.
Docker Image SizesCPU
CUDA
XPU
|
Signed-off-by: Zakharov, Ivan <ivan.zakharov@intel.com>
Signed-off-by: Zakharov, Ivan <ivan.zakharov@intel.com>
ivanzati
requested review from
MarkRedeman,
maxxgx,
rajeshgangireddy and
sys-geti
as code owners
July 30, 2026 13:33
ivanzati
temporarily deployed
to
windows-msix-signing
July 30, 2026 13:34 — with
GitHub Actions
Inactive
ivanzati
temporarily deployed
to
windows-msix-signing
July 30, 2026 13:34 — with
GitHub Actions
Inactive
ivanzati
temporarily deployed
to
windows-msix-signing
July 30, 2026 13:34 — with
GitHub Actions
Inactive
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 3 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
.github/renovate.json5:31
- The new comment claims lockfile maintenance should keep the default
recreateWhen: "always"and not inherit the repo-levelrecreateWhen: "never", but there is norecreateWhenoverride insidelockFileMaintenance. As written, this is internally inconsistent and (given the PR title) risks documenting the opposite behavior from what is intended for closed uv.lock PRs. Consider making the intended behavior explicit here and updating the comment accordingly.
// Keep the default `recreateWhen: "always"` (do not inherit the top-level
// "never") so a fresh lock PR is opened whenever new lock changes appear.
// These PRs are immortal by design; that is acceptable now that the lock
// no longer reintroduces blocked CVEs and is mergeable.
AlexanderBarabanov
approved these changes
Jul 31, 2026
rajeshgangireddy
approved these changes
Jul 31, 2026
ivanzati
deleted the
ivanzati/renovate-uv-lock-do-not-update-when-pr-closed
branch
July 31, 2026 13:04
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Description
Exclude CVE-flagged torch 2.6.0+xpu from project toml. The issue is identified to appear when win32 and py3.14 with torch+xpu is required. Thus fixing it to py3.13 and excluding darwin as it's build in CI remains commented out.
✨ 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.