Repository navigation
Automate sentry-dotnet version bumps with Dependabot (weekly) #126
Description
The sentry-dotnet SDK version is pinned by hand in `dependencies/Sentry.properties` (and its transitive deps in the sibling `*.properties` files). It drifts whenever nobody manually bumps it — see #125.
Set up Dependabot (or equivalent automation) to open weekly PRs that bump the `version = ...` line in `dependencies/Sentry.properties` to the latest stable sentry-dotnet release. Ideally the automation also re-runs `dependencies/download.ps1` so the lockstep with the cached `modules/Sentry/lib/` is maintained, but at minimum a PR that just edits the properties file would be enough to keep things visible.
Dependabot doesn't natively understand the `.properties` format, so this likely needs a custom GitHub Action on a weekly cron rather than a stock `dependabot.yml` entry.
Related: #125.
Activity
linear-code commentedon May 22, 2026
POWERSH-14
jamescrosswell commentedon May 25, 2026
Already implemented — closing.
The daily
update-depsworkflow (.github/workflows/update-deps.yml) usesgetsentry/github-workflows/updater@v3to bumpdependencies/Sentry.propertiesand open a PR with a CHANGELOG entry. It runs on cron (0 3 * * *), on every push tomain, and via manual dispatch — more frequent than the weekly cadence this issue asked for.PR #109 is a live example of it working (5.16.1 → 6.5.0).
Not covered by the current automation: re-running
dependencies/download.ps1to refreshmodules/Sentry/lib/and the sibling transitive*.propertiesfiles. If that lockstep drift causes a real problem in future, we'll open a focused issue for it then.