chore(ci): add triage guide to Renovate dependency dashboard #54

2026-05-08T17:08:24+02:00

julien commented

2026-05-08 17:08:24 +02:00

Summary

The Renovate dashboard organises pending updates in standard sections (Open / Awaiting Schedule / Pending Approval / Detected dependencies / …). The section headings alone aren't self-explanatory, so the patch+minor vs major distinction we set up via dependencyDashboardApproval: true for majors gets lost in the noise.

Add a dependencyDashboardHeader markdown block that:

maps each section → the triage action expected (batch-merge / leave alone / read-changelog-then-tick);
re-states the pinned constraints visible right at the top: Prisma majors blocked per ADR-0006, Trivy/gitleaks workflow pins not Renovate-tracked;
cross-links to docs/development.md for the full procedure (lighter CI on bot PRs, etc.).

Test plan

After merge, trigger Renovate manually (Actions → Renovate → Run workflow).
The "Renovate Dependency Dashboard" issue body now starts with the triage table; sections below are unchanged.
Pending major bumps (e.g. anything Renovate now holds for approval) are clearly distinguishable from the patch/minor batch.

After this PR

Triage the dashboard with the new guide; once that wave is digested, on to A — local infra recipe.

## Summary The Renovate dashboard organises pending updates in standard sections (Open / Awaiting Schedule / Pending Approval / Detected dependencies / …). The section headings alone aren't self-explanatory, so the patch+minor vs major distinction we set up via `dependencyDashboardApproval: true` for majors gets lost in the noise. Add a `dependencyDashboardHeader` markdown block that: - maps each section → the triage action expected (batch-merge / leave alone / read-changelog-then-tick); - re-states the pinned constraints visible right at the top: Prisma majors blocked per ADR-0006, Trivy/gitleaks workflow pins not Renovate-tracked; - cross-links to `docs/development.md` for the full procedure (lighter CI on bot PRs, etc.). ## Test plan - [ ] After merge, trigger Renovate manually (Actions → Renovate → Run workflow). - [ ] The "Renovate Dependency Dashboard" issue body now starts with the triage table; sections below are unchanged. - [ ] Pending major bumps (e.g. anything Renovate now holds for approval) are clearly distinguishable from the patch/minor batch. ## After this PR Triage the dashboard with the new guide; once that wave is digested, on to **A — local infra recipe**.

julien added 1 commit 2026-05-08 17:08:25 +02:00

chore(ci): add triage guide to Renovate dependency dashboard

CI / commits (pull_request) Successful in 1m9s

Details

CI / check (pull_request) Successful in 1m16s

Details

CI / scan (pull_request) Successful in 1m16s

Details

CI / a11y (pull_request) Successful in 38s

Details

CI / perf (pull_request) Successful in 1m31s

Details

857e8de11c

The dashboard issue Renovate maintains lists pending updates in a
handful of sections (Open / Awaiting Schedule / Pending Approval /
Detected dependencies / …) but the section headings alone are not
self-explanatory — easy to lose the patch+minor vs major
distinction we put in place via `dependencyDashboardApproval` for
majors.

Add a `dependencyDashboardHeader` markdown block that maps each
section to the triage action it expects from the maintainer:
which to batch-merge, which to leave alone, which to read the
changelog before approving. Re-state the pinned constraints
(Prisma majors blocked until the Prisma 7 ADR per ADR-0006; the
Trivy / gitleaks pins in workflow YAML which Renovate doesn't see).
Cross-link to docs/development.md for the full procedure.

Re-renders on the next Renovate run (no code change required —
the header is part of the dashboard issue body).

julien merged commit 8f81b6202e into main

2026-05-08 17:14:33 +02:00

julien deleted branch chore/ci/renovate-dashboard-triage-header

2026-05-08 17:14:34 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: julien/apf_portal#54