o-nikolas opened a new pull request, #72167: URL: https://github.com/apache/airflow/pull/72167
While preparing provider documentation the release manager is asked whether a provider has any changes apart from doc-only. Answering **no** marks the provider as doc-only and writes the `.latest-doc-only-change.txt` marker. Answering **yes** instead classifies each change individually — and that per-change classification can conclude that every change is documentation after all (`classify_provider_pr_files` returning `documentation`). In that case `get_most_impactful_change` returns `TypeOfChange.DOCUMENTATION`, so no version is bumped — correct — but nothing wrote the marker file. The next wave then replays exactly the same changes and asks about them again. The same function already handles this correctly in its other branch (when the release manager declines the proposed version), so this is an inconsistency rather than a deliberate difference. Hit while preparing the 2026-08-25 provider wave: google was doc-only despite the answer, and the marker had to be written by hand. **Tested:** new test in `dev/breeze/tests/test_provider_documentation.py` asserting the marker is written and `PrepareReleaseDocsChangesOnlyException` is raised; verified it fails without the source change. All 66 tests in that file pass, and `prek run --from-ref upstream/main --stage pre-commit` is clean. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Kiro CLI (claude-fable-5) Generated-by: Kiro CLI (claude-fable-5) 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]
