Prepare providers release 2026-08-06 - #71219
Merged
Merged
Conversation
Re-cut of the 2026-08-01 wave, whose vote was cancelled: it carried the pandas cap that has since been reverted, and enough providers were affected that trimming them one at a time would have left little to vote on. Clickhousedb drops out of the wave - its 1.0.1 was never published, so it goes back to 1.0.0 and the change rides a later release. Opensearch moves to a minor because the wave now adds a public 'from_config' and registers a log scheme.
potiuk
requested review from
Lee-W,
dheerajturaga,
gopidesupavan,
jscheffl,
kaxil,
o-nikolas,
shahar1,
shubhamraj-git and
vincbeck
as code owners
August 6, 2026 07:31
Contributor
|
LGTM, Thanks for the re cut |
vatsrahul1001
approved these changes
Aug 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Re-cut of the 2026-08-01 wave, whose vote was cancelled.
That wave shipped #70791 (cap pandas below 3 for DataFrame XComs), which has since been reverted in #71100 and replaced by proper pandas 3 support in #71103. Enough of the 48 providers carried the cap that trimming them one at a time would have left little to vote on, so the whole wave is re-cut instead.
Versions are unchanged from 2026-08-01 except where noted below — nothing from that wave was published, so the same numbers go out again (as rc2, or rc3 for the four that were already at rc2).
Changes relative to the cancelled wave
clickhousedb leaves the wave. Its
1.0.1was never published — onlyrc1/rc2tags exist — so it returns to1.0.0andChange Clickhouse lifecycle to incubation (#69166)rides a later release.opensearch escalates to a minor,
1.11.2→1.12.0. #70295 adds a publicOpensearchRemoteLogIO.from_config()and registers theopensearchscheme inprovider.yaml, which a patch bump cannot carry.The pandas cap is collapsed rather than reverted in place. #70791 added the cap and #71100 removed it, both within this unreleased wave, so the net user-facing change is nil. Publishing "pandas limited to < 3" followed by "revert pandas limited to < 3" would describe a restriction no user ever received. Both PRs are recorded in the excluded block of the 14 affected providers instead.
Post-cut commits folded in: #71145 (snowflake), #71055 (apache.spark), #70651 and #71046 (common.ai), #70939 (fab), #71078 (amazon, google, microsoft.azure, yandex), #70870 (edge3), #70538 (git), #71106 (google docs).
gitkeeps#70538under Misc at0.4.2. It swaps a releasedAirflowExceptionforValueErrorinGitHook, which is a user-visible change, but it is a deliberate step toward the project's "no broad AirflowException" standard and not worth a major bump on a 0.x provider.Not included
keycloakis intentionally left unfolded — more PRs are expected there, and the remediations for #70550 (#71077, #70981) are still open.Validation
--reapply-templates-onlyis idempotent (byte-identical on re-run)... note::blocks.(#NNNN), internal jargon, or an unnamed dependency bump.update-providers-next-versionis a no-op — no# use next versionpins remain.allow provider dependency bumplabel needed: no inter-provider>=floor changed. The onlypyproject.tomledits are clickhousedb's and opensearch's own version strings.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 5 (1M context) following the guidelines