Renovate reopens closed PR #25665
Answered
by
rarkins
klippx
asked this question in
Request Help
Renovate reopens closed PR
#25665
-
How are you running Renovate?Self-hosted If you're self-hosting Renovate, tell us what version of Renovate you run.39.0.5 If you're self-hosting Renovate, select which platform you are using.github.com Was this something which used to work for you, and then stopped?It used to work, and then stopped Wanted end result.When I close a PR and keep the branch, renovate should detect that I do not want this change and stop trying to reopen it. What you tried so far.It works for some branches such as Here is the config: {
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"gitAuthor": "Renovate Bot <bot@renovateapp.com>",
"onboarding": false,
"platform": "github",
"repositories": ["repo-xxx/graphql-federation-mono"],
"labels": ["dependencies"],
"extends": ["config:js-app", ":disableDependencyDashboard"],
"prHourlyLimit": 2,
"prConcurrentLimit": 16,
"postUpdateOptions": ["yarnDedupeHighest"],
"platformAutomerge": true,
"commitMessageSuffix": "`[skip cd]`",
"packageRules": [
{
"matchUpdateTypes": ["major"],
"commitMessageSuffix": null,
"automerge": false
},
{
"matchUpdateTypes": ["patch", "minor"],
"matchCurrentVersion": "!/^0/",
"automerge": true
},
{
"matchUpdateTypes": ["pin", "digest"],
"automerge": true
}
],
"lockFileMaintenance": {
"enabled": true,
"automerge": true
}
}So the difference AFAICT seems to be the presence of Relevant debug logsLogsIn these details then |
Beta Was this translation helpful? Give feedback.
Answered by
rarkins
Nov 9, 2023
Replies: 1 comment 2 replies
-
|
https://docs.renovatebot.com/key-concepts/pull-requests/#immortal-prs |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Oh, so this is because of Only unique version PRs can be ignored¶Renovate can only ignore PRs if they have a unique version, like "to v16.1.2" or "to v16" in the title. And Grouped updates with different versions¶The problem comes when there are groups of updates which have different versions. Then the update becomes "Update react (major)", which is not safely ignorable, instead of "Update react to v16". |
Beta Was this translation helpful? Give feedback.
-
|
Yes. We are looking into improvements of this in #22251 The challenge is:
|
Beta Was this translation helpful? Give feedback.
Answer selected by
klippx
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes. We are looking into improvements of this in #22251
The challenge is: