Closed SimonCropp closed 1 year ago
I'm on vacation. Hopefully I can get back to this in about a week.
The build fails, probably cause you've dropped support for older .NET targets, and now refer to files that does not exist. Why was support for older frameworks dropped?
expecto dropped support for older frameworks
The build passes, but I noticed it still installed .NET 3.1 and 5. Could you update the workspace files to no longer do that as well? Then I think this update would be good. Just have to make sure it triggers a new minor (not patch) release.
done
@Alxandr let's bump a major version of this package
If nothing comes up with 0.14 in about a month or so, I agree it's probably a good idea - but I do not want to release a 1.0 right after making a breaking change.
Why not? It is perfect reason to do that 🙂
Cause I want to make sure it's stable first.
BREAKING-CHANGE: major expecto update and drops support for older .NET framework versions.