Update provider metadata after the 2026-08-06 providers release - #71338
Open
potiuk wants to merge 1 commit into
Open
Update provider metadata after the 2026-08-06 providers release#71338potiuk wants to merge 1 commit into
potiuk wants to merge 1 commit into
Conversation
potiuk
requested review from
eladkal,
jscheffl,
shahar1 and
vincbeck
as code owners
August 9, 2026 01:20
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
1 participant
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.
Regenerated
generated/provider_metadata.jsonafter the 2026-08-06 providersrelease (44 providers published to PyPI and
dist/release).Produced by
breeze release-management generate-providers-metadata --refresh-constraints-and-airflow-releases; the diff is 176 added linescovering exactly the 44 released versions.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines