[Dependencies] Constraint flask to version ~=3.1.0 (rather than ~=3.0) to reduce the risk of breaking changes. #7078
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.
Description of changes
Constraint flask to version ~=3.1.0 (rather than ~=3.0) to reduce the risk of breaking changes.
According to Flask release notes, there may be breaking changes in minor releases. See release notes for 3.1.0.
Constraining to 3.1.x is also suggested by Dependabot in #6568 and it is consistent with the approach we applied before the recent upgrade in #6932. In fact, before that change we used to constraint to the minor (flask>=2.2.5,<2.3).
Tests
This change does not alter the version of Flask tested in #6932 (i.e. 3.1.2), but simply limit future updates within the same minor. No additional test required.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.