apache-airflow-providers-imap

Changelog¶

3.8.0¶

Note

This release of provider is only available for Airflow 2.9+ as explained in the Apache Airflow providers support policy.

Misc¶

Bump minimum Airflow version in providers to Airflow 2.9.0 (#44956)

3.7.0¶

Note

This release of provider is only available for Airflow 2.8+ as explained in the Apache Airflow providers support policy.

Misc¶

Bump minimum Airflow version in providers to Airflow 2.8.0 (#41396)

3.6.1¶

Misc¶

Faster 'airflow_version' imports (#39552)
Simplify 'airflow_version' imports (#39497)

3.6.0¶

Note

This release of provider is only available for Airflow 2.7+ as explained in the Apache Airflow providers support policy.

Misc¶

Bump minimum Airflow version in providers to Airflow 2.7.0 (#39240)

3.5.0¶

Note

This release of provider is only available for Airflow 2.6+ as explained in the Apache Airflow providers support policy.

Misc¶

Bump minimum Airflow version in providers to Airflow 2.6.0 (#36017)

3.4.0¶

Note

This release of provider is only available for Airflow 2.5+ as explained in the Apache Airflow providers support policy.

Misc¶

Bump min airflow version of providers (#34728)

3.3.2¶

Misc¶

Improve modules import in Airflow providers by some of them into a type-checking block (#33754)

3.3.1¶

Misc¶

Simplify conditions on len() in other providers (#33569)

3.3.0¶

In case of IMAP SSL connection, the context now uses the “default” context

The “default” context is Python’s default_ssl_context instead of previously used “none”. The default_ssl_context provides a balance between security and compatibility but in some cases, when certificates are old, self-signed or misconfigured, it might not work. This can be configured by setting “ssl_context” in “imap” configuration of the provider. If it is not explicitly set, it will default to “email”, “ssl_context” setting in Airflow.

Setting it to “none” brings back the “none” setting that was used in previous versions of the provider, but it is not recommended due to security reasons and this setting disables validation of certificates and allows MITM attacks.

You can also override “ssl_context” per-connection by setting “ssl_context” in the connection extra.

Features¶

Allows to choose SSL context for IMAP provider (#33108)
Add possibility to use 'ssl_context' extra for SMTP and IMAP connections (#33112)

3.2.2¶

Note

This release dropped support for Python 3.7

Misc¶

Add note about dropping Python 3.7 for providers (#32015)

3.2.1¶

Misc¶

Bring back min-airflow-version for preinstalled providers (#31469)

3.2.0 (YANKED)¶

Warning

This release has been yanked with a reason: This version might cause unconstrained installation of old airflow version lead to Runtime Error.

Note

This release of provider is only available for Airflow 2.4+ as explained in the Apache Airflow providers support policy.

3.1.1¶

Misc¶

[misc] Get rid of 'pass' statement in conditions (#27775)

3.1.0¶

Note

This release of provider is only available for Airflow 2.3+ as explained in the Apache Airflow providers support policy.

Misc¶

Move min airflow version to 2.3.0 for all providers (#27196)

3.0.0¶

Breaking changes¶

Note

This release of provider is only available for Airflow 2.2+ as explained in the Apache Airflow providers support policy.

2.2.3¶

Bug Fixes¶

Fix mistakenly added install_requires for all providers (#22382)

2.2.2¶

Misc¶

Add Trove classifiers in PyPI (Framework :: Apache Airflow :: Provider)

2.2.1¶

Misc¶

Support for Python 3.10

2.2.0¶

Features¶

Add "use_ssl" option to IMAP connection (#20441)

2.1.0¶

Features¶

Allow setting port in IMAP Connection (#20440)

2.0.1¶

Misc¶

Optimise connection importing for Airflow 2.2.0

2.0.0¶

Breaking changes¶

Auto-apply apply_default decorator (#15667)

Warning

Due to apply_default decorator removal, this version of the provider requires Airflow 2.1.0+. If your Airflow version is < 2.1.0, and you want to install this provider version, first upgrade Airflow to at least version 2.1.0. Otherwise your Airflow package version will be upgraded automatically and you will have to manually run airflow upgrade db to complete the migration.

1.0.1¶

Updated documentation and readme files.

1.0.0¶

Initial version of the provider.