Skip to content

Conversation

@gmarciani
Copy link
Contributor

@gmarciani gmarciani commented Nov 4, 2025

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.

@gmarciani gmarciani requested review from a team as code owners November 4, 2025 21:07
@gmarciani gmarciani added dependencies Pull requests that update a dependency file 3.x labels Nov 4, 2025
Copy link
Contributor

@hehe7318 hehe7318 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR title should be ....(rather than ~=3.0)...

No blocking comment. Approved!

@gmarciani gmarciani changed the title [Dependencies] Constraint flask to version ~=3.1.0 (rather than ~=3.1) to reduce the risk of breaking changes. [Dependencies] Constraint flask to version ~=3.1.0 (rather than ~=3.0) to reduce the risk of breaking changes. Nov 4, 2025
@gmarciani gmarciani enabled auto-merge (rebase) November 4, 2025 21:12
@gmarciani gmarciani merged commit 997bf59 into aws:develop Nov 4, 2025
30 checks passed
@gmarciani gmarciani deleted the wip/mgiacomo/3150/flask-version-1104-1 branch November 4, 2025 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.x dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants