shahar1 opened a new pull request, #70258: URL: https://github.com/apache/airflow/pull/70258
Three changelog-entry defects slipped through a real provider-release wave prepared with the `prepare-providers-documentation` skill and were only caught in maintainer review. This adds the rules that would have prevented them. 1. **Collapse within-wave "add then rename/rework" chains into one net entry.** The Kafka provider added a listener (#68082) and renamed it to the Kafka Event Producer (#70014) in the same unreleased wave. Following "one commit subject per entry" produced two disconnected lines — `Add ... event listener (#68082)` under Features and `Rename Kafka Listener to Kafka Event Producer (#70014)` under Misc — so a reader can't tell the net change is "a Kafka Event Producer was introduced," and the introducing PR is decoupled from the rename. The rule now writes one entry describing the net change and naming all involved PRs. This is the changelog counterpart of the already-merged unreleased-feature classification rule. 2. **Capitalize every entry's first letter**, not only after stripping a Conventional Commit prefix (contributors ship lowercase subjects like `derive keycloak ...`). 3. **Send no-PR release-tooling commits to the excluded block** even when breeze's deterministic classifier labeled them `documentation` (`Prepare ... release`, `Hide non-user-facing entries ...`) — a `(#NNNN)`-less line in a visible section reads as a mistake. Plus a Phase 5 scan that greps the new sections for all three defects before hand-off. Docs/skill-only change — no runtime behavior affected. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 4.8, 1M context) Generated-by: Claude Code (Opus 4.8, 1M context) 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]
