Dropping support for a framework should be a major semver change

[tillig]

We have some devs that are working solely on .NET 6 at the moment without 8 installed. We noticed that in v0.8.0 the support for .NET 6 was dropped. That's a breaking change from a consumer perspective. Could I ask that future changes involving dropping framework support be a major version number? At least we'd know to look for something breaking.

[bjorkstromm]

Actually SemVer spec states the following:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

However, I feel your pain and sorry for removing .NET 6 support. I could try adding it back if you want 🙂

Also curious to know how you are using Depends?

[tillig]

My usage is usually around managing things related to security audits. Our code goes through several scanners and sometimes figuring out what thing is including a transitive dependency opens up alternatives to fixing things beyond just "add a direct reference." For example, if we see the problem transitive dependency is brought in by one of our own common libraries, we can make the update in one spot and update the existing reference instead of having all the extra transitives.

Don't worry about re-adding .NET 6 since it's going out of lifecycle soon anyway, but if you could maybe do a major increment for breakers like that next time, it would be super duper awesome. I think adding framework support could totally be a 0.1.0 increment, but dropping... the major change would just be nice.