Resolve common.ai common-compat next-version pin missed in 2026-06-16 wave#68740
Merged
Merged
Conversation
The 2026-06-16 provider wave (apache#68642) was merged without running 'breeze release-management update-providers-next-version', so common.ai's dependency on apache-airflow-providers-common-compat was left at the placeholder '>=1.14.1 # use next version' instead of being bumped to the 1.15.0 released in the same wave. Resolve the pin and regenerate the provider dependencies metadata and docs.
shahar1
added
allow provider dependency bump
skip common compat check
amoghrajesh
approved these changes
Jun 19, 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
2 participants
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.
Human Summary
Missed running "update-providers-next-version" while using the prepare-docs skill, so I left out common.ai # use next version unattended. This PR fixes it.
AI Summary
Click here
The 2026-06-16 provider documentation wave (#68642) was merged without running `breeze release-management update-providers-next-version`. As a result, `common.ai` was left depending on `apache-airflow-providers-common-compat>=1.14.1 # use next version` — the placeholder pin — instead of `>=1.15.0`, the common-compat version released in that same wave.This resolves the pin to
>=1.15.0, removes the# use next versioncomment, and regenerates the affected build metadata and docs
(
provider_dependencies.json+ checksum,README.rst,docs/index.rst).It is exactly the diff
update-providers-next-versionwould have producedhad it run before the wave merged.
common.aiwas the only providercarrying a
# use next versioncomment, so no other provider is affected.A companion PR (#68739) adds the missing step to the
prepare-providers-documentationskill and the release guide so this is notforgotten again.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines