Add net9.0 to the list <TargetFrameworks>

[lipchev]

This also applies for the official v5 branch, but I'm more interested in doing it for the v6-release.

A lot of the packages are way out of date - so the build is failing. The packages are of course updated locally, but the actual Directory.Packages.props is 6 months old...

Do you think there is any work required for the build workflow?

Would you like me to prepare a PR (updating the packages and adding net9.0 to the list of <TargetFrameworks>)?

[angularsen]

I fixed the failing build, it was due to a vulnerability in Nuget.Protocol nuget.

We can definitely add net9, I haven't really given much thought into how we should deal with LTS vs STS versions of dotnet. Maybe we should just add the latest LTS and all following releases?

[lipchev]

I fixed the failing build, it was due to a vulnerability in Nuget.Protocol nuget.

We can definitely add net9, I haven't really given much thought into how we should deal with LTS vs STS versions of dotnet. Maybe we should just add the latest LTS and all following releases?

Yeah that seems about right.. and netstandard forever 😆

PS I just recently realized we still haven't moved to net8.0 yet..

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.