Why

• airflow.utils.timezone is now resolved at runtime by a module-level __getattr__. mypy cannot see dynamically produced attributes, so from airflow.utils import timezone fails with Module "airflow.utils" has no attribute "timezone" [attr-defined].
• The mypy-providers hook only checks files included in the current push diff, so these pre-existing failures cannot be detected until an unrelated change happens to touch an affected file.

How

• Replace the imports with from airflow.providers.common.compat.sdk import timezone.

Was generative AI tooling used to co-author this PR?

• Yes - Claude Code

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.