Fix SQLAlchemy version to v1.4.27, as v1.4.28 #1114
Merged
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.
🧰 Issue
Fixes #1112.
🚀 Overview:
SQLAlchemy v1.4.28 emits more warnings in various situations (see here. These warnings are triggered by various geoalchemy functions we use. In our CI, we have it set to turn warnings into errors - which is a good idea in general, but means that we can get unexpected errors from dependencies being upgraded by minor point releases which change warnings rules.
The requirement for SQLAlchemy just required v1.4.x, which is normally ok as breaking changes shouldn't occur in a point release - but this doesn't apply to warnings. So, this PR fixes the version to v1.4.27.
There is already a PR in geoalchemy2 to fix these warnings, so once that PR is merged and a new version is released, then we can stop fixing the point version.
🤔 Reason:
Fix CI.
🔨Work carried out:
Confirmations
interactive_review
if reviewers will need to see UI\docs
folderalembic revision
transitions📝 Developer Notes: