Npgsql: Adjust .NET support and version numbers on CI #695
Conversation
| @@ -42,8 +42,8 @@ jobs: | |||
| fail-fast: false | |||
| matrix: | |||
| os: [ 'ubuntu-latest' ] | |||
| dotnet-version: [ '6.0.x', '7.0.x', '8.0.x' ] | |||
| npgsql-version: [ '6.0.11', '7.0.7', '8.0.3' ] | |||
| dotnet-version: [ '7.0.x', '8.0.x', '9.0.x' ] | |||
There was a problem hiding this comment.
.NET 7 is no longer maintained while .NET 6 is (until November 2024). Would it make sense to wait for .NET 9 to be released (currently only released as RC)?
There was a problem hiding this comment.
.NET 6
.NET 6 is maintained until November 2024.
Interesting. I think the build started failing on .NET 6 the other day, that's why I removed that slot.
-- https://github.com/crate/cratedb-examples/actions/runs/11358160147/job/31592225551
If you can find a different solution, we can keep that version. Otherwise, we may be able to bring it back later, when applicable, and when a solution can be found?
I definitively don't want to terminate validation of .NET 6 too early, this is probably just a CI hiccup, hopefully. My main intention was to spend a little amount of time to make the build succeed again, in order to prepare the Build Status page for the weekend.
On the other hand, November 2024 will be just around the corner, so, should we bother and investigate at all?
There was a problem hiding this comment.
.NET 7
.NET 7 is no longer maintained.
Oh. Thanks. Do you think we should remove it from the CI matrix?
There was a problem hiding this comment.
.NET 9
Would it make sense to wait for .NET 9 to be released (currently only released as RC)?
We are not doing any super strong promises here. I am always happy to unlock CI slots as soon as artefacts of major releases become available, even as RC versions, so our assets can be tested on them from the very beginning.
If you don't have any objections against that philosophy, let's embrace it?
There was a problem hiding this comment.
Do you think we should remove it from the CI matrix?
As long as it doesn't hurt us, we can keep it.
don't want to terminate validation of .NET 6 too early
.NET 6 is gone next month anyway, so let's remove it instead of spending time on figuring out why it failed. It is unlikely any user will complain.
About
References