Renovate拆分主次版本PR时出现版本冲突问题求助

团队使用setup.cfg管理Python包，配置Renovate工具时遇到以下情况：

• 内部包托管于Azure Artifactory
• 已配置Renovate为主版本、次版本更新分别创建独立PR和分支，但拆分PR时出现包冲突
• 将主次版本更新合并为单个PR时无冲突，但希望保持拆分PR的配置

配置文件 #

{
"platform": "azure",
"onboardingPrTitle": "Renovate PR ${process.env.BUILDNUMBER}",
"prBody": "This PR updates dependencies to their latest versions.",
"prTitle": `Renovatebot Update: ${process.env.BUILDNUMBER}`,
"branchPrefix": "feature/",
"endpoint": "https://dev.azure.com/***",

"token": process.env.RENOVATE_TOKEN,
"hostRules": [
{
"matchHost": "pypi.org/simple",
"hostType": "pypi",
"enabled": true
},
{
"matchHost": "pkgs.dev.azure.com/**/_packaging//pypi/simple/",
"hostType": "pypi",
"enabled": true,
"username": "****",
"password": process.env.PYPI_PASSWORD
}
],
packageRules: [
{
updateTypes: ["major"],
groupName: "all major updates"
},
{
updateTypes: ["minor", "patch"],
groupName: "all non-major updates"
},
{
matchPaths: ["*pyproject.toml"],
managers: ["poetry"]
}
],
enabledManagers: ["poetry"],
poetry: {
fileMatch: ["(^|/)pyproject.toml$"],
enabled: true
},
"lockFileMaintenance": {
"enabled": true
},
onboarding: true,
onboardingConfig: {
extends: ['config:base']
},
branchPrefix: 'feature/renovate/',
separateMajorMinor: true,
separateMinorPatch: false, // This line indicates that minor and patch updates will not be separated
labels: ['dependencies'],
prConcurrentLimit: 5,
prHourlyLimit: 5,
schedule: ['at any time'],
rangeStrategy: 'bump',
"repositories": ["test/renovate-test-smart"]
};

流水线日志 #

WARN: artifactErrors (repository=test/renovate-test-smart, branch=feature/renovate/major-all-major-updates) "artifactErrors": [ { "lockFile": "poetry.lock", "stderr": "Updating dependencies\nResolving dependencies...\n\nWarning: Found deprecated key 'default' or 'secondary' in pyproject.toml configuration for source standard. Please provide the key 'priority' instead. Accepted values are: 'default', 'primary', 'secondary', 'supplemental', 'explicit'.\nWarning: Found deprecated priority 'default' for source 'standard' in pyproject.toml. You can achieve the same effect by changing the priority to 'primary' and putting the source first.\nThe currently activated Python version 3.10.12 is not supported by the project (~3.9).\nTrying to find and use a compatible version. \nUsing python3.9 (3.9.21)\n\nThe current project's supported Python range (>=3.9,<3.10) is not compatible with some of the required packages Python requirement:\n  - numpy requires Python >=3.10, so it will not be satisfied for Python >=3.9,<3.10\n\nBecause numpy (2.2.3) requires Python >=3.10\n and no versions of numpy match >2.2.3,<3.0.0, numpy is forbidden.\nSo, because smartcapturing depends on numpy (^2.2.3), version solving failed.\n\n  • Check your dependencies Python requirement: The Python requirement can be specified via the pythonormarkersproperties\n    \n    For numpy, a possible solution would be to set thepython property to \"<empty>\"\n\n    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,\n    [https://python-poetry.org/docs/dependency-specification/#using-environment-markers\n\"]](https://python-poetry.org/docs/dependency-specification/#using-environment-markers\n%22) } ]
INFO: Comment added (repository=test/renovate-test-smart, branch=feature/renovate/major-all-major-updates) "issueNo": 240714, "topic": "⚠️ Artifact update problem"
INFO: Repository finished (repository=test/renovate-test-smart) "cloned": true, "durationMs": 38457

从日志可见，拆分PR时的冲突根源是主版本更新的numpy 2.2.3要求Python >=3.10，但项目自身仅支持Python 3.9。合并PR时Renovate可能自动协调依赖（比如同步更新Python版本或选择兼容的依赖版本），但单独处理主版本更新时无法解决该兼容问题。可按以下步骤处理：

1. 调整项目Python版本范围

   • 若团队可升级Python，将pyproject.toml中的Python版本限制修改为>=3.10，即可兼容numpy 2.x版本。
   • 若暂无法升级Python，需在Renovate配置中排除numpy的主版本更新，或指定numpy仅更新到兼容3.9的最高版本（如1.x系列）。

2. 优化Renovate分组规则

   • 对存在版本依赖关联的包（如Python版本和numpy），在packageRules中添加分组规则，将相关更新放在同一PR中，避免单独更新引发冲突。示例：

     {
       "matchPackageNames": ["numpy", "python"],
       "groupName": "python-numpy-compatible-updates"
     }
     

3. 修复pyproject.toml废弃配置

   • 日志提示default优先级配置已废弃，将pyproject.toml中源配置的default改为priority = "primary"，并确保该源排在首位，消除依赖解析的潜在问题。

4. 调整Renovate的rangeStrategy

   • 当前rangeStrategy: 'bump'会直接将依赖版本范围提升到最新主版本，可改为widen让版本范围包含兼容旧版本，或replace指定具体兼容版本，减少不兼容更新触发。

内容的提问来源于stack exchange，提问作者Tamilselvan