Apache Airflow version

2.3.1 (latest released)

What happened

As of Airflow 2.3.0 the airflow db check-migrations -t 0 command will ALWAYS think there are unapplied migrations (even if there are none to apply), whereas, in Airflow 2.2.5, a single check would be run succeessfully.

This was caused by PR #18439, which updated the loop from while True (which always loops at least once) to for ticker in range(timeout) (which will NOT loop if timeout=0).

What you think should happen instead

No response

How to reproduce

No response

Operating System

All

Versions of Apache Airflow Providers

No response

Deployment

Other

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

• I agree to follow this project's Code of Conduct