shivaam commented on issue #71246:
URL: https://github.com/apache/airflow/issues/71246#issuecomment-5229109759

   Tested four changes that were not already reported in the issue comments, 
using exact PyPI RC artifacts in clean venvs with Airflow 3.3.0; all passed:
   
   - #69712 — `apache-airflow-providers-sftp==6.0.1rc2` and 
`apache-airflow-providers-ssh==6.0.1rc2` naturally resolved Paramiko 5.0.0, 
imported from the installed artifacts, and validated RSA private keys with 
`rsa-sha2-512`. The 6.0.0 controls retain the Paramiko `<5` cap and reproduce 
the old `KeyError: 'ssh-rsa'` when Paramiko 5 is deliberately forced.
   - #70539 — ArangoDB `2.9.6rc2` raises the intended built-in `ValueError` for 
a missing collection operation; the 2.9.5 control raises `AirflowException`, 
and valid insert dispatch remains intact.
   - #70538 — Git `0.4.2rc2` raises the intended built-in `ValueError` for 
conflicting connection keys; the 0.4.1 control raises `AirflowException`, and 
single-key construction remains intact.
   - #70373 — Neo4j `3.12.1rc2` includes deprecated `sql` in the standard 
template/rendering pipeline, renders it, and passes the rendered query to the 
hook; 3.12.0 was used as the control.
   
   I also ran a real Airflow 3.3.0 Breeze deployment with the exact RC 
artifacts installed from PyPI and mounted provider sources disabled. A focused 
DAG parsed without import errors and completed successfully through the 
scheduler and LocalExecutor: the artifact-identity gate and the behavior tasks 
for the four items above passed. The API health check reported the metadata DB, 
scheduler, triggerer, and DAG processor healthy. No live external provider 
services or credentials were used.
   
   No issues found.
   
   ---
   Drafted-by: OpenAI Codex (GPT-5.6); reviewed by @shivaam before posting
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to