[FrankYang0529]

Why

• The akeyless, hashicorp and smtp providers all import conf with from airflow.providers.common.compat.sdk import conf in

airflow/providers/akeyless/src/airflow/providers/akeyless/secrets/akeyless.py

Line 28 in b3b62fa

from airflow.providers.common.compat.sdk import conf

airflow/providers/hashicorp/src/airflow/providers/hashicorp/secrets/vault.py

Line 27 in b3b62fa

from airflow.providers.common.compat.sdk import conf

airflow/providers/smtp/src/airflow/providers/smtp/notifications/smtp.py

Line 26 in b3b62fa

from airflow.providers.common.compat.sdk import conf

• common.compat.sdk only contains conf in common-compat 1.12.0 (Source conf from airflow.sdk.configuration.conf for apache providers #59966).
• The three pyproject.toml files still declare apache-airflow-providers-common-compat>=1.8.0 (akeyless, hashicorp) and >=1.10.1 (smtp).

How

• Bump apache-airflow-providers-common-compat to >=1.12.0 in the three pyproject.toml files.

---

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.