shahar1 opened a new pull request, #68738: URL: https://github.com/apache/airflow/pull/68738
While preparing the 2026-06-16 provider documentation wave (#68642), two providers with breaking changes — `edge3` 4.0.0 (Edge execution-API `TaskInstanceDTO` schema change) and `common.ai` 0.5.0 (SQLToolset `allowed_tables` now enforced on queries) — got the `Breaking changes` bullet but no top-of-version `.. note::` explaining *what* breaks or *how* users should adapt. The cause is in the `prepare-providers-documentation` skill: it instructed the agent to add the `.. note::` block **only** for the Airflow min-version bump case. Yet every provider `changelog.rst` carries the standing convention in its header — *"only add notes … when there are some breaking changes and you want to add an explanation to the users on how they are supposed to deal with them"* — so a behavioural breaking change should always get an explanatory note. This updates the skill (Phase 4b rules and the incremental Phase 4 step) so the `.. note::` block covers both situations: the Airflow min-version bump *and* every `breaking` classification, with the breaking-change note written from the PR description and diff so readers learn how to react without opening the PR. Docs-only change to an agent skill; no runtime code affected. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 4.8) Generated-by: Claude Code (Opus 4.8) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
