Also, here is some additional context you might not have. For that one we involved Vespa engineers beyond Radu. Tomas, the pyvespa maintainer looked at our CI failures, and we worked together to make pyvespa "nicer" and better "suited" for Airflow. He is also marked as steward of Vespa provider together with Radu so wecan reach out to them as needed. And it's been a very good cooperation so far - they even bumped dependencies of pyvespa to match ours due to security reasons ( https://github.com/vespa-engine/pyvespa/pull/1229).
That change with Vespa was actually pretty involving and we worked together with the steward to work out the best "setup" for it :) . So I personally think everything there is "cool" (or even beyond cool compared to some of our past cross-provider interaction) But yeah - if we could do better here and you think we need to fix something - I am all ears :) . But I can't see too much to improve. J. On Thu, Apr 23, 2026 at 1:27 PM Jarek Potiuk <[email protected]> wrote: > And just to add - we often do that- when a cross-provider forces us to > bump the minimum version, and we often bump the version without any > explanation. We have a general "rule": the constraints we generate ensure > that any set of our "latest" providers can be installed "together" when we > want to use the latest Airflow. That's our general "golden rule" here. So - > at least for me, this is one of the clearest explanations one could expect > :). > > I would love to hear, though. Perhaps you would like a more detailed > explanation? > > I was involved in figuring that one out - so I might provide more context. > > Those cross-provider dependencies are often difficult to "explain" in > layman's language, because there are some 3 or 4 levels of indirection > between "why" we set certain limits. In this case - as far as I recall - > the reason was that when we tried to install the "lowest direct > dependencies" on those "ssh" providers, they had some weird interaction > between installed dependent libraries. > Installing a higher version of Paramiko, followed by installing a lower > version, caused some (I think) underlying x509 library to crash—apparently, > the lower-level library was not prepared for the migration up and down. So > we figured that the easiest way to prevent issues for both our CI and our > users is to bump the minimum in SSH and SFTP. > > But I would have **really** a hard time trying to explain it "better" in > the changelog - but maybe you thought about some other messaging we could > use? What would you propose in this case? > > J. > > > On Thu, Apr 23, 2026 at 1:15 PM Jarek Potiuk <[email protected]> wrote: > >> Hey Elad, >> >> But it's - IMHO - cler explained in the changelog: >> >> >> https://airflow.staged.apache.org/docs/apache-airflow-providers-ssh/5.0.1/changelog.html >> >> https://airflow.staged.apache.org/docs/apache-airflow-providers-sftp/stable/changelog.html >> >> SSH: >> >> 5.0.1¶ >> Release Date: 2026-04-22 >> >> Misc¶ >> Bump paramiko lower bound to >=3.5.1 due to adding Vespa provider (#63988) >> >> SFTP" >> >> Changelog¶ >> 5.7.4¶ >> Release Date: 2026-04-22 >> >> Misc¶ >> Bump paramiko lower bound to >=3.5.1 due to adding Vespa provider (#63988) >> >> Why do you think it needs more explanation? We usually do not do more >> explanation when we bump minimum version - and here the explanation is >> quite clear ? >> >> J. >> >> >> >> On Thu, Apr 23, 2026 at 1:02 PM Elad Kalif <[email protected]> wrote: >> >>> -1 (binding) for ssh and sftp providers. >>> the changes in these providers are bumping paramiko min version which >>> came >>> from a PR that adds vespa provider >>> https://github.com/apache/airflow/pull/63988#discussion_r3130238616 >>> There is no indication into why version was bumped and seems like we >>> missed >>> it during review. >>> Even if the version needs to be bumped that is not normally how we do it >>> and generally lets leave this to when >>> https://github.com/apache/airflow/pull/64898 is resolved. >>> >>> On Thu, Apr 23, 2026 at 1:01 PM Wei Lee <[email protected]> wrote: >>> >>> > +1 (binding), checked: >>> > >>> > - SVN >>> > - in Docker installation >>> > - Reproducible package builds >>> > - Licence >>> > - Signature >>> > - Checksums >>> > >>> > Best regards, >>> > Wei Lee >>> > >>> > Shahar Epstein <[email protected]> 於 2026年4月23日週四 上午7:55寫道： >>> > >>> > > Hey all, >>> > > >>> > > I have just cut the new wave Airflow Providers packages with release >>> > > preparation date 2026-04-21. This email is calling a vote on the >>> release, >>> > > which will last for 72 hours - which means that it will end on >>> 2026-04-25 >>> > > 23:54 UTC and until 3 binding +1 votes have been received. >>> > > >>> > > >>> > > Consider this my (binding) +1. >>> > > Please note that we have an RC for a new provider, Vespa - I'd like >>> to >>> > ask >>> > > the stewards to test it well before shipping its first version >>> (v0.1.0). >>> > > >>> > > >>> > > Airflow Providers are available at: >>> > > https://dist.apache.org/repos/dist/dev/airflow/providers/2026-04-21 >>> > > >>> > > *apache-airflow-providers-2026-04-21-source.tar.gz* is the full >>> source >>> > > tarball of airflow repo - snapshot taken at the moment of provider's >>> > > release. >>> > > >>> > > *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience >>> python >>> > > "sdist" distributions that we publish in PyPI >>> > > >>> > > *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python >>> > > "wheel" distributions that we publish in PyPI. >>> > > >>> > > The test procedure for PMC members is described in >>> > > >>> > > >>> > >>> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-pmc-members >>> > > >>> > > The test procedure for and Contributors who would like to test this >>> RC is >>> > > described in: >>> > > >>> > > >>> > >>> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-contributors >>> > > >>> > > >>> > > Public keys are available at: >>> > > https://dist.apache.org/repos/dist/release/airflow/KEYS >>> > > >>> > > Please vote accordingly: >>> > > >>> > > [ ] +1 approve >>> > > [ ] +0 no opinion >>> > > [ ] -1 disapprove with the reason >>> > > >>> > > Only votes from PMC members are binding, but members of the >>> community are >>> > > encouraged to test the release and vote with "(non-binding)". >>> > > >>> > > Please note that the version number excludes the 'rcX' string. >>> > > This will allow us to rename the artifact without modifying >>> > > the artifact checksums when we actually release it. >>> > > >>> > > The status of testing the providers by the community is kept here: >>> > > https://github.com/apache/airflow/issues/65702 >>> > > >>> > > The issue is also the easiest way to see important PRs included in >>> the RC >>> > > candidates. >>> > > Detailed changelog for the providers will be published in the >>> > documentation >>> > > after the >>> > > RC candidates are released. >>> > > >>> > > You can find the RC packages in PyPI following these links: >>> > > >>> > > https://pypi.org/project/apache-airflow-providers-amazon/9.26.0rc1/ >>> > > >>> > >>> https://pypi.org/project/apache-airflow-providers-apache-kafka/1.13.3rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-celery/3.19.0rc1/ >>> > > >>> > > >>> > >>> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.16.1rc1/ >>> > > >>> https://pypi.org/project/apache-airflow-providers-common-ai/0.1.1rc1/ >>> > > >>> https://pypi.org/project/apache-airflow-providers-common-sql/1.35.0rc1/ >>> > > >>> https://pypi.org/project/apache-airflow-providers-databricks/7.13.0rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-edge3/3.5.0rc1/ >>> > > >>> > >>> https://pypi.org/project/apache-airflow-providers-elasticsearch/6.5.3rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-fab/3.6.2rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-google/21.2.0rc1/ >>> > > >>> https://pypi.org/project/apache-airflow-providers-hashicorp/4.6.0rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-jdbc/5.4.4rc1/ >>> > > >>> > > >>> > >>> https://pypi.org/project/apache-airflow-providers-microsoft-azure/13.1.2rc1/ >>> > > >>> https://pypi.org/project/apache-airflow-providers-openlineage/2.15.0rc1/ >>> > > >>> https://pypi.org/project/apache-airflow-providers-opensearch/1.9.1rc1/ >>> > > >>> https://pypi.org/project/apache-airflow-providers-papermill/3.13.0rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-sendgrid/4.2.3rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-sftp/5.7.4rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-smtp/3.0.0rc1/ >>> > > >>> https://pypi.org/project/apache-airflow-providers-snowflake/6.12.2rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-ssh/5.0.1rc1/ >>> > > https://pypi.org/project/apache-airflow-providers-vespa/0.1.0rc1/ >>> > > >>> > > Cheers, >>> > > Shahar Epstein >>> > > >>> > >>> >>
