-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update renovate config #1495
Update renovate config #1495
Conversation
Change-type: patch
.github/renovate.json
Outdated
"packageRules": [ | ||
{ | ||
"matchUpdateTypes": ["major", "minor", "patch", "digest"], | ||
"groupName": "only-manually-bumped-packages", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need a groupName if enabled == false.
.github/renovate.json
Outdated
"matchUpdateTypes": [ | ||
"major", | ||
"minor" | ||
], | ||
"automerge": false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need an automerge setting if enabled == false.
"automerge": false, | ||
"labels": ["renovate", "dependencies", "{{depType}}", "major"] | ||
"enabled": false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you really want renovate to never open a PR for this, or would you like it to open a PR for convenience but never rebase it and disable automerge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's a major or a minor, which has a dependency of the proxy being bumped & deployed first, I think it makes sense to avoid opening the PR completely. I expect that who-ever does such a minor or major, will anyway have to bump it everywhere as part of shipping their project.
Also, atm concurrent PRs can break others & count against the SDK test users' ratelimiting, so this keeps the SDK test runners free for a bit longer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack, as long as you're okay with creating more PRs by hand
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like I have always done :) especially for our own packages
475f1f8
to
d9711c1
Compare
.github/renovate.json
Outdated
@@ -1,11 +1,16 @@ | |||
{ | |||
"extends": ["github>balena-io/renovate-config"], | |||
"prConcurrentLimit": 1, | |||
"prConcurrentLimit": 3, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you increasing this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
B/c I expect that prHourlyLimit: 1
might help enough and having just 1 starving PR sounds like renovate will always be blocked. I can start w/ leaving prConcurrentLimit: 1
as it was and only increase it later if you prefer.
Yea let me do that...
Change-type: patch
Change-type: patch
Change-type: patch
d9711c1
to
545bf72
Compare
a5ff553
Resolves: #
HQ:
See:
Depends-on:
Change-type: major|minor|patch
Contributor checklist