Describe the bug
OOTB the csproj format doesn't support version ranges.
However, we use major versions to indicate breaking changes across packages.
This may result in errors when updating one of many packages, for example when dependabot is updating them one-by-one.
Expected behavior
We'd like to limit the package dependencies on the last major version published to prevent this from accidentally happening. And, it will give a clearer understanding why a dependabot update is failing.
Package+Version: All
Framework version: All
Describe the bug OOTB the csproj format doesn't support version ranges. However, we use major versions to indicate breaking changes across packages. This may result in errors when updating one of many packages, for example when dependabot is updating them one-by-one.
Expected behavior We'd like to limit the package dependencies on the last major version published to prevent this from accidentally happening. And, it will give a clearer understanding why a dependabot update is failing.
Additional context Maybe this answer to this article helps: https://stackoverflow.com/a/73098203