Currently dependabot manages upgrading nuget packages but a Specflow update actually updates multiple packages.
Dependabot sees these as separate and so opens a PR for each one, with each build then failing.
So each time there's a Specflow release I have to manually bump the version. This is something that could be automated.
Look at how hard it'd be to automate this (could run an action on a PR being raised, so still using dependabot to detect the new version of Specflow) and then detect whether the change that has been made is a Specflow version bump.
If it's not simple, it's probably not worth automating...
Currently dependabot manages upgrading nuget packages but a Specflow update actually updates multiple packages. Dependabot sees these as separate and so opens a PR for each one, with each build then failing. So each time there's a Specflow release I have to manually bump the version. This is something that could be automated.
Look at how hard it'd be to automate this (could run an action on a PR being raised, so still using dependabot to detect the new version of Specflow) and then detect whether the change that has been made is a Specflow version bump.
If it's not simple, it's probably not worth automating...