potiuk opened a new pull request, #74733:
URL: https://github.com/apache/airflow/pull/74733

   Ad-hoc provider release re-cutting the four providers excluded from the 
2026-10-06 wave (#74459), now that the regressions found during that vote are 
fixed:
   
   - **amazon 9.38.0** — AWS auth manager login fix (#74529), plus the changes 
merged since the wave cut.
   - **dbt.cloud 4.11.0** — deferred tasks with tenacity `retry_args` (#74489).
   - **google 22.7.0** — GKE operator imports with older `cncf-kubernetes` 
(#74505).
   - **common.ai 1.0.0** — first stable release, replacing the never-published 
0.11.0; `SandboxToolset` deep-copy (#74525) and HITL review output types 
(#74537) fixed. Four breaking changes, each with a migration note in the 
changelog (#74721, #74385, #74396, #74450).
   - **common.compat 1.22.0** — added to the wave: amazon's new 
`EmrServerlessGetSessionEndpointOperator` (#70766) imports `mask_secret` from 
`common.compat.sdk`, which no released common.compat exports, so amazon now 
requires `common-compat>=1.22.0`.
   
   amazon, dbt.cloud and google were cut as rc1 but never published, so their 
changelog sections are extended rather than bumped. Fixes for regressions that 
never shipped are folded into the entry of the change they fix.
   
   This PR raises an inter-provider `>=` floor (amazon → common-compat), so it 
needs the `allow provider dependency bump` label.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Opus 5
   
   Generated-by: Claude Opus 5 following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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