Target net8 so we can use the latest version of Npgsql
#24
Conversation
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
|
@rofr I'm in the process of tidying up the code read to be handed over to other maintainers (including you if you are still interested). This seems like a significant decision, wondering if there were thoughts. |
I'm no longer involved in any projects using dbup with postgres. The project in question was actually canceled so I'm neither invested enough nor have sufficient knowledge to be helpful as a maintainer. And for this change I don't really see any options other than going to net8. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Looks like
Npgsqlhas dropped support fornetstandard2.0so in order to keep on top of patches this library should do the same. Going to net8.0 as it's the only supported LTS.