#8276: Updating Npgsql to 4.0.17 and fixing setup with PostgreSQL #8810
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
…osest major version that isn't vulnerable) https://github.com/OrchardCMS/Orchard/security/dependabot/54
…in different tables, which is not supported by PostgreSQL
BenedekFarkas
changed the title
sebastienros
approved these changes
Dec 5, 2024
# Conflicts: # src/Orchard.Web/packages.config
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.
Fixes #8276
Originally wanted to upgrade Npgsql from 2.2.3 to the suitable version that isn't vulnerable, but the setup was also failing due to index names in Projections not being unique across tables.
I closed the original dependabot PR (#8796) to work on this based on 1.10.x and then that will be merged into dev.