Update renovate to @42 stops creating new PRs on bitbucket #39242
Unanswered
Kr0san89
asked this question in
Request Help
Replies: 1 comment 10 replies
-
|
According to https://github.com/renovatebot/renovate/releases/tag/42.0.0 there has been a change wrt minimumReleaseAge. Maybe that is affecting you? |
Beta Was this translation helpful? Give feedback.
10 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate
Which platform you running Renovate on?
Bitbucket
Which version of Renovate are you using?
42.6.0
Please tell us more about your question or problem
I Updated renovate from version 41 to 42 and since then i didn't get any new PRs for updates
I always had in the config the option
"minimumReleaseAge": "3 days",in that regard the behaivour should not have ben changed
I did find an older comment on a similar issue here: #14724
and tried around with those configurations
"prNotPendingHours":72, "prCreation": "immediate", "minimumReleaseAgeBehaviour": "timestamp-optional",but none of them really changed anything
so i rolled back to version 41 and PRs are coming in again, i pasted logs for v42 & v41 run regarding an example for angular-eslint-monorepo rule (v41 was run after v42)
Not sure why i'm now in that yellow state and also a bit unclear why we don't want to create a PR when the branch is older it looks a bit strange to me.
renovate/lib/workers/repository/update/pr/index.ts
Lines 251 to 264 in f7d7c8a
Logs (if relevant)
Relevant Logs
Log angular-eslint v42
Log angular-eslint v41
Beta Was this translation helpful? Give feedback.
All reactions