continuwuation/continuwuity

Fork 85

ci: `Renovate` commits too frequently, and too often breaks linting on `main` branch #1517

New issue

Closed

opened 2026-03-09 05:37:23 +00:00 by gamesguru · 5 comments

gamesguru commented

2026-03-09 05:37:23 +00:00

Contributor

Also there are just too many PRs open in general by Renovate.

I wanna look at what people have open, but every time I have to click the "labels" menu and hide "Dependencies/Renovate" to filter the spam.

Someone please find a solution to this distracting issue!! Thank you

Given our release cadence of about once a month or so, I think it would be preferable to "batch up" all low-impact Renovate/automated package security update PRs into a weekly or twice a month merge, one which ideally is tested (perhaps manually) for linter compliance. Also there are just too many PRs open in general by Renovate. I wanna look at what people have open, but every time I have to click the "labels" menu and hide "Dependencies/Renovate" to filter the spam. Someone please find a solution to this distracting issue!! Thank you

gamesguru changed title from ~~git: Renovate commits too frequently, and too often breaks linting on main branch~~ to gitea: Renovate commits too frequently, and too often breaks linting on main branch

2026-03-09 12:04:23 +00:00

lveneris commented

2026-03-09 12:27:30 +00:00

Contributor

If not, however, this would be trivial to resolve. The solution can be as simple as adding minor to matchUpdateTypes for more groups.

The part I find weird personally is that some PRs use chore(deps): and others use fix(deps):

The renovate config already implements batching for patch-level dependency updates. I'd say you could batch minor-level updates too, as is already done for Actions, but this appears to have been a deliberate decision by the maintainers, presumably to inspect minor-level and above updates to dependencies individually. If not, however, this would be trivial to resolve. The solution can be as simple as adding `minor` to `matchUpdateTypes` for more groups. The part I find weird personally is that some PRs use `chore(deps):` and others use `fix(deps):`

lveneris commented

2026-03-09 12:36:42 +00:00

Contributor

cc @Jade, do you have any objections to batching all non-major cargo dependency updates, or am I correct in assuming the intention is to allow you to inspect minor releases?

Jade commented

2026-03-09 12:39:33 +00:00

Owner

CI failures on renovate commits to main are because they are usually merged in quick sequence, causing earlier runs to be cancelled.

If you inspect the currently open PRs, you will notice that most of them have errors. They need manual work, while the ones we have merged do not. This is why most updates are not bundled.

The label is there so you can filter out these PRs.

CI failures on renovate commits to main are because they are usually merged in quick sequence, causing earlier runs to be cancelled. If you inspect the currently open PRs, you will notice that most of them have errors. They need manual work, while the ones we have merged do not. This is why most updates are not bundled. The label is there so you can filter out these PRs.

👍 1

Jade commented

2026-03-09 12:43:07 +00:00

Owner

Also, afaik renovate is not rust-semver aware by default so bundling all minor updates would bundle breaking changes in zerover crates.

lveneris commented

2026-03-09 12:46:54 +00:00

Contributor

That was what I noticed too, it counts minor releases as minor releases even for projects in a 0.y.z state, which is a problem. You could get around that, but half of the Rust ecosystem is 0.y.z anyway. Are there non-zerover crates that have required manual intervention for minor releases? If not, we could batch minor updates for packages above version 1.0.0, I suppose.

It is also worth noting that Renovate makes up a whole third of the merged PR volume, so cutting that down wouldn't hurt.

lveneris referenced this issue from a pull request that will close it,

2026-03-09 14:53:04 +00:00

chore: update cargo renovate rules #1519

nex changed title from ~~gitea: Renovate commits too frequently, and too often breaks linting on main branch~~ to ci: Renovate commits too frequently, and too often breaks linting on main branch

2026-03-09 16:16:35 +00:00

nex added the

Bug

Dependencies

Rows
Columns

ci: Renovate commits too frequently, and too often breaks linting on main branch #1517

ci: `Renovate` commits too frequently, and too often breaks linting on `main` branch #1517