Skip to content

Prepare providers release 2026-08-06 - #71219

Merged
potiuk merged 1 commit into
apache:mainfrom
potiuk:prepare-providers-release-2026-08-06
Aug 6, 2026
Merged

Prepare providers release 2026-08-06#71219
potiuk merged 1 commit into
apache:mainfrom
potiuk:prepare-providers-release-2026-08-06

Conversation

@potiuk

@potiuk potiuk commented Aug 6, 2026

Copy link
Copy Markdown
Member

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.1 was never published — only rc1/rc2 tags exist — so it returns to 1.0.0 and Change Clickhouse lifecycle to incubation (#69166) rides a later release.

opensearch escalates to a minor, 1.11.21.12.0. #70295 adds a public OpensearchRemoteLogIO.from_config() and registers the opensearch scheme in provider.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).

git keeps #70538 under Misc at 0.4.2. It swaps a released AirflowException for ValueError in GitHook, 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

keycloak is intentionally left unfolded — more PRs are expected there, and the remediations for #70550 (#71077, #70981) are still open.

Validation

  • --reapply-templates-only is idempotent (byte-identical on re-run).
  • No misplaced .. note:: blocks.
  • 13 added changelog entries, none with a lowercase start, missing (#NNNN), internal jargon, or an unnamed dependency bump.
  • update-providers-next-version is a no-op — no # use next version pins remain.
  • No allow provider dependency bump label needed: no inter-provider >= floor changed. The only pyproject.toml edits are clickhousedb's and opensearch's own version strings.
Was generative AI tooling used to co-author this PR?
  • Yes — Claude Opus 5 (1M context)

Generated-by: Claude Opus 5 (1M context) following the guidelines

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.
@vatsrahul1001

Copy link
Copy Markdown
Contributor

LGTM, Thanks for the re cut

@potiuk
potiuk merged commit 55b35f7 into apache:main Aug 6, 2026
118 checks passed
@potiuk
potiuk deleted the prepare-providers-release-2026-08-06 branch August 6, 2026 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants