Hunteerq opened a new issue, #55757:
URL: https://github.com/apache/airflow/issues/55757
### Apache Airflow version
2.11.0
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
All our Astronomer's webserver that runs apache airflow changed status to
unhealthy from 12th of September. Recent logs show following error:
```
[2025-09-16T15:14:17.296+0000] {configuration.py:1237} WARNING - No module
named 'flask_limiter.wrappers'
```
We noticed that Flask-Limiter version got automatically updated from 3.12 to
3.13 by following dependencies:
```
flask-limiter==3.13
# via flask-appbuilder
flask-appbuilder==4.5.3
# via apache-airflow-providers-fab
apache-airflow==2.11.0
# via
# -c (workspace)
# apache-airflow-providers-amazon
# apache-airflow-providers-common-compat
# apache-airflow-providers-common-io
# apache-airflow-providers-common-sql
# apache-airflow-providers-fab
# apache-airflow-providers-ftp
# apache-airflow-providers-http
# apache-airflow-providers-imap
# apache-airflow-providers-microsoft-mssql
# apache-airflow-providers-sftp
# apache-airflow-providers-slack
# apache-airflow-providers-smtp
# apache-airflow-providers-snowflake
# apache-airflow-providers-sqlite
# apache-airflow-providers-ssh
# apache-airflow-providers-tableau
# astronomer-cosmos
```
Specifying `Flask-Limiter==3.12` in our pyproject.toml forces airflow to use
that version and solves the issue
### What you think should happen instead?
Flask's dependencies should be set in stone, so there are no unexpected
updates
### How to reproduce
Deploy specified airflow's version, webserver could have same errors
### Operating System
gitlab-runner 17.11.0
### Versions of Apache Airflow Providers
_No response_
### Deployment
Astronomer
### Deployment details
_No response_
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]