Clarify unreleased-feature changes are not breaking in provider-doc skill#70255
Merged
shahar1 merged 1 commit intoJul 22, 2026
Merged
Conversation
…kill Renaming or removing a symbol that was introduced within the same unreleased provider-release wave never reached users, so the AI-driven classification must not treat it as a breaking change and force a spurious major version bump. Anchor the breaking-change checklist on whether the affected symbol shipped in a released version.
vincbeck
approved these changes
Jul 22, 2026
stephen-bracken
pushed a commit
to stephen-bracken/airflow
that referenced
this pull request
Jul 22, 2026
…kill (apache#70255) Renaming or removing a symbol that was introduced within the same unreleased provider-release wave never reached users, so the AI-driven classification must not treat it as a breaking change and force a spurious major version bump. Anchor the breaking-change checklist on whether the affected symbol shipped in a released version.
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.
The
prepare-providers-documentationskill drives AI classification of provider PRs into version bumps. Its breaking-change checklist flagged any public-symbol removal/rename as breaking, without checking whether the affected symbol had ever been released.During a real release wave this produced a false positive: the Kafka provider added
KafkaListenerPlugin(#68082) and renamed it to the Kafka Event Producer (#70014) within the same unreleased wave. The rename tripped the "public class renamed, no shim" rule and proposed a spurious major bump (1.x → 2.0), even though users never received the old name.This change anchors the checklist on a released-only precondition: before classifying a removal/rename as breaking, confirm the symbol existed at the provider's last release tag. A within-wave rename of a brand-new operator/plugin is feature-shaped, not a major bump.
Docs/skill-only change — no runtime or user-facing behavior is affected.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8, 1M context) following the guidelines