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.
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.