Skip to content
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

Merged
4 commits merged into from
Nov 18, 2024
Merged

Update renovate config #1495

4 commits merged into from
Nov 18, 2024

Conversation

thgreasi
Copy link
Member

Resolves: #
HQ:
See:
Depends-on:
Change-type: major|minor|patch


Contributor checklist
  • Includes tests
  • Includes typings
  • Includes updated documentation
  • Includes updated build output

@thgreasi thgreasi changed the title Update renovate Update renovate config Nov 15, 2024
"packageRules": [
{
"matchUpdateTypes": ["major", "minor", "patch", "digest"],
"groupName": "only-manually-bumped-packages",
Copy link
Contributor

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.

"matchUpdateTypes": [
"major",
"minor"
],
"automerge": false,
Copy link
Contributor

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
Copy link
Contributor

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?

Copy link
Member Author

@thgreasi thgreasi Nov 15, 2024

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.

Copy link
Contributor

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

Copy link
Member Author

@thgreasi thgreasi Nov 15, 2024

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

@@ -1,11 +1,16 @@
{
"extends": ["github>balena-io/renovate-config"],
"prConcurrentLimit": 1,
"prConcurrentLimit": 3,
Copy link
Contributor

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?

Copy link
Member Author

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...

@flowzone-app flowzone-app bot closed this pull request by merging all changes into master in a5ff553 Nov 18, 2024
@flowzone-app flowzone-app bot deleted the update-renovate branch November 18, 2024 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants