lyrathorpe/renovate-config
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

config: tune concurrency, security scheduling, stability, noise #52

Merged
lyrathorpe merged 1 commits from config/tuning into main 2026-06-16 14:52:18 +01:00
Conversation 0 Commits 1 Files Changed 1
+5 -4
lyrathorpe commented 2026-06-16 14:44:55 +01:00
Owner
Copy Link
Copy Source
  • Concurrency limits: prConcurrentLimit 50 → 10, branchConcurrentLimit 5 → 10 (every PR needs a branch, so the old 5 made the 50 meaningless).
  • Security bypass: vulnerabilityAlerts.schedule = ["at any time"] so weekend CVE fixes aren't held until Monday by the weekday schedule.
  • Stability buffer: minimumReleaseAge: "3 days" so releases age before they're opened/automerged.
  • Drop assignees (same single user as reviewers) — noise on every PR, including auto-merged ones.

Closes #46
Closes #47
Closes #48
Closes #49

- **Concurrency limits**: `prConcurrentLimit` 50 → 10, `branchConcurrentLimit` 5 → 10 (every PR needs a branch, so the old 5 made the 50 meaningless). - **Security bypass**: `vulnerabilityAlerts.schedule = ["at any time"]` so weekend CVE fixes aren't held until Monday by the weekday `schedule`. - **Stability buffer**: `minimumReleaseAge: "3 days"` so releases age before they're opened/automerged. - **Drop `assignees`** (same single user as `reviewers`) — noise on every PR, including auto-merged ones. Closes #46 Closes #47 Closes #48 Closes #49
lyrathorpe added 1 commit 2026-06-16 14:44:55 +01:00
config: tune concurrency, security scheduling, stability, noise 653934dc98 
- Reconcile concurrency limits: prConcurrentLimit 50 -> 10 and
  branchConcurrentLimit 5 -> 10 (every PR needs a branch, so the old 5 capped
  effective PRs and made 50 meaningless).
- Let vulnerability updates bypass the weekday schedule
  (vulnerabilityAlerts.schedule = at any time) so weekend CVE fixes are not
  held until Monday.
- Add minimumReleaseAge = 3 days so a release ages before it is opened or
  automerged (guards against broken/yanked releases).
- Drop redundant assignees (same single user as reviewers) -- noise on every
  PR, including auto-merged ones.

Closes #46
Closes #47
Closes #48
Closes #49
lyrathorpe merged commit 3f2d51015b into main 2026-06-16 14:52:18 +01:00
lyrathorpe deleted branch config/tuning 2026-06-16 14:52:21 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate-bot lyrathorpe
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lyrathorpe/renovate-config#52
Delete Branch "config/tuning"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?