-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Npgsql: Adjust .NET support and version numbers on CI #695
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.NET 6
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.NET 7
Oh. Thanks. Do you think we should remove it from the CI matrix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.NET 9
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as it doesn't hurt us, we can keep it.
.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.