[MISC] UV configuration for renovate#38
Conversation
| // Exclude Renovate PRs from auto-generated release notes | ||
| "labels": ["not bug or enhancement"], | ||
| "enabledManagers": ["poetry", "github-actions", "regex"], | ||
| "enabledManagers": ["poetry", "pep621", "github-actions", "regex"], |
There was a problem hiding this comment.
The manager is pep621, lockFileMaintenance from line 11 will make renovate updated the uv.lock as well.
| { | ||
| "matchManagers": ["pep621"], | ||
| "matchDepNames": ["python"], | ||
| "matchDatasources": ["python-version"], |
There was a problem hiding this comment.
I think we can merge with the poetry rule above based on datasource.
| "matchManagers": ["pep621"], | ||
| "rangeStrategy": "in-range-only", | ||
| "matchJsonata": [ | ||
| "depType = 'dependency-groups' and managerData.depGroup = 'charm-libs'" |
carlcsaposs-canonical
left a comment
carlcsaposs-canonical
left a comment
There was a problem hiding this comment.
Dependabot vulnerability alerts—which Renovate uses to segment security updates from normal PRs (and to open security update PRs immediately, instead of waiting for the weekly schedule)—do not currently support uv.lock
|
|
discussed in backlog grooming: waiting here for 26.04 *craft tools changes to test all of them and valuate complete migration to uv for all repos. There are several blockers right now here (c) @carlcsaposs-canonical . |
4 participants
UV presets, in case we switch permanently.
Tested on https://github.com/dragomirp/pgbouncer-operator/pull/9