Skip to content

chore: Repo-level Renovate configuration - #2145

Open
NickJosevski wants to merge 1 commit into
mainfrom
nj/renovate-repo-config
Open

NickJosevski wants to merge 1 commit into
mainfrom
nj/renovate-repo-config

Conversation

@NickJosevski

@NickJosevski NickJosevski commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Background

Renovate has been installed since January with no configuration. renovate.json holds only a schema reference. The schedule in renovate-dependencies.yml stays commented out. Every dependency bump in the history was written by hand, including the ones that closed advisories.

This PR adds the configuration. Turning the schedule on is a separate decision.

Results

  • Weekly run. Advisories run on their own schedule with a security label.
  • osvVulnerabilityAlerts adds the OSV database on top of GitHub's alerts.
  • The AWS SDK, the Azure SDK, the NuGet client, Serilog, and the test dependencies each land as one PR.
  • Majors queue on the dependency dashboard for approval.
  • Workflow actions update monthly and pin by digest.
  • Test fixtures and the publish output are ignored. No automerge.

Validated with renovate-config-validator.

How to review this PR

General quality. The grouping is the one judgment call: fewer PRs, coarser review granularity.

Reducing risk

  • Nothing runs from this PR. The scheduled trigger stays commented out.
  • Confirm RENOVATE_GITHUB_TOKEN belongs to an org member before turning the schedule on. TeamCity filters PR builds to MEMBER. The 12 Dependabot PRs have never built for that reason.
  • The Octopus group stays quiet until the runner has feedz.io credentials.
  • global.json and the release branches are out of scope.

🤖 Generated with Claude Code

@NickJosevski
NickJosevski force-pushed the nj/renovate-repo-config branch from a0158de to 0303123 Compare September 17, 2026 06:38
renovate.json held only a schema reference before this change.

Group the SDK families and the test dependencies. Each group lands as one PR.
Advisories run on their own schedule with a security label. Majors queue on
the dependency dashboard for approval. Targets main only.

The scheduled trigger in renovate-dependencies.yml stays commented out.
Nothing runs yet.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@NickJosevski
NickJosevski force-pushed the nj/renovate-repo-config branch from 0303123 to 10da593 Compare September 17, 2026 06:43
@NickJosevski
NickJosevski marked this pull request as ready for review September 17, 2026 08:10
@NickJosevski NickJosevski changed the title Draft: repo-level Renovate configuration Repo-level Renovate configuration Sep 17, 2026
@NickJosevski NickJosevski changed the title Repo-level Renovate configuration chore: Repo-level Renovate configuration Sep 17, 2026
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.

1 participant