Romfos

@dtchepak no, I i think make sense to stabilize and release what we have now and then continue working on the next version

@dtchepak could you please prepare 6.0.0 release?

Problem is that ms slowly stopping support .NET Standard 2.0 properly in modern nuget packages and slowly go away from it For example: one of the dependency for RabbitMQ.Client ...

@paulomorgado you can check my screenshot above about warning for support and testing some additional articles: - https://andrewlock.net/stop-lying-about-netstandard-2-support/ - https://github.com/open-telemetry/opentelemetry-dotnet/issues/3448

@paulomorgado this screenshot related to .net standard support for some runtimes like .net 5, .net core 3.1, .net fx .4.6.1

@paulomorgado that is the one of the problem. you can check links from my post above note: no difference for .net standard 2.0 support for net fx 4.6.1 and 4.6.2...

@lukebakken 1) I don't have CONCRETE example for version 7 that you can build + run 2) Support old runtimes - this is not what i propose 3) Yes, NET...

Teams members of NSubstitute are very conservative about update dependencies... I have 2 questions: 1) Do we want to have dependabot with update proposals? cc @NSubstitute team 2) Do we...

> > if you are worried around certain packages needing to be pinned to a specific version, > > I'm less worried about packages NSub uses, and more about requirements...

@dtchepak according to you comment here: https://github.com/nsubstitute/NSubstitute/pull/831#discussion_r1817846412 If I right understand your comment. We want to stay on older dependencies for package project We can enable it for non-package projects...