potiuk commented on issue #70953: URL: https://github.com/apache/airflow/issues/70953#issuecomment-5178008070
Thanks everyone for the testing — the status issue is updated, 15 more boxes ticked. **Confirmed working and checked off:** | PR | Provider | Verified by | |---|---|---| | #69786 | airbyte 6.0.1rc1 | Steve Ahn (dev@) | | #69676 / #70569 / #70330 | amazon 9.34.0rc1 | Steve Ahn (dev@) / @AlejandroMorgante / @MannXo | | #68679 | apache.spark 6.3.1rc1 | @onlyarnav | | #70325 | cohere 1.6.7rc1 | @MannXo | | #69736 / #69893 | common.sql 2.1.0rc1 | Steve Ahn (dev@) / @aaron-y-chen | | #70478 | fab 3.8.0rc1 | @justinpakzad | | #70504 | google 22.3.0rc2 | @aaron-y-chen | | #70301 | microsoft.azure 14.1.0rc1 | @Andrushika, Andrew Chang (dev@) | | #70332 / #70874 | snowflake 6.16.0rc1 | @justinpakzad | | #70480 | standard 1.17.0rc1 | @raphaelauv | | #70326 | weaviate 3.4.1rc1 | @MannXo | Special thanks for the depth of several of these — real AWS DMS full-load-and-CDC runs, before/after comparisons against the previous release that pin the actual behaviour change, and a real Azurite round-trip rather than a mock. **The following six providers are being removed from the 2026-08-01 wave** and will be re-cut once the fixes land: - **keycloak 0.9.0rc1** — #70800 (`KeycloakJWTMiddleware`) does not set the Airflow JWT correctly on 3.3.0 and the login redirect-loops; #70550 sits on top of it and additionally needs limiting to 3.3.0+ (#70981). - **clickhousedb 1.0.1rc2** — the release carries only the lifecycle metadata change (#69166), which does not warrant a release of its own. - **amazon 9.34.0rc1**, **microsoft.azure 14.1.0rc1**, **google 22.3.0rc2**, **yandex 4.5.1rc1** — the secrets-backend team-scoping work (#70878, #70876, #70899, #70869, #70877, #70736) refuses to resolve any connection / variable / config id containing the team-namespace separator, unconditionally — including in deployments that never enabled multi-team. An ordinary id containing `--` (or `__` on Azure, which normalises `_` to `-` before the check) is silently treated as missing, with only a `log.warning`. Fix is in #71078. The checkmarks already earned on those six stay ticked and carry over to the re-cut, so testers do not need to repeat that work. **Still open, not a removal:** there is a temporary -1 on dev@ against anything carrying #70791 (limiting pandas to <3 for DataFrame XComs) pending a catch-up on the reasoning. That touches 14 providers in this wave (amazon, apache.hdfs, apache.hive, common.sql, databricks, exasol, google, papermill, postgres, presto, salesforce, snowflake, trino, weaviate) and also affects Airflow core, so it is being resolved on the dev list rather than by pulling providers. One housekeeping note raised in this thread: GitHub only renders the first 50 @-mentions in an issue body, so contributors past that cut-off were never notified and found the RC through the vote email instead. Worth a follow-up comment mentioning the rest. --- Drafted-by: Claude Code (Opus 5); reviewed by @potiuk 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]
