Prepare providers release 2026-04-21#65614
Conversation
3e12ad1 to
33b2f7f
Compare
19c295a to
cc7fc5e
Compare
|
Just to verify if we want to wait for https://redirect.github.com/apache/airflow/pull/65594 cc @ashb |
potiuk
left a comment
There was a problem hiding this comment.
Thanks for cutting the wave — I spotted one small follow-up on the SMTP reclassification. See inline on providers/smtp/provider.yaml. Separately, @eladkal's note about moving the top-level breaking-change narrative under the 3.0.0 heading in providers/smtp/docs/changelog.rst looks like it still needs to be addressed in the latest push.
Everything else checks out: all 18 providers have matching versions across provider.yaml / pyproject.toml / __init__.py / README.rst / docs/index.rst; changelog categories match the bump kind (Features → minor, only Bug Fixes/Misc → patch, Breaking changes → major); uv.lock versions match; providers/.last_release_date.txt and all source-date-epoch values are on 2026-04-21.
cc7fc5e to
5824240
Compare
5824240 to
9977bc8
Compare
DataflowHook imported BeamHook, BeamRunnerType, and beam_options_to_args at module level, making the entire google provider fail to import when apache-airflow-providers-apache-beam is not installed. apache-beam is not a declared dependency of the google provider, so this hard import was always incorrect. The import error surfaced during the provider release process (apache#65614) when the provider yaml check script imports all registered provider modules and beam was not present in the environment. Move the imports to lazy form inside the two methods that actually use them: DataflowHook.__init__ and DataflowHook._build_gcloud_command.
16ccc0a to
2861833
Compare
2861833 to
3d40c5e
Compare
Prepare providers release 2026-04-21