Dev-iL commented on PR #75062: URL: https://github.com/apache/airflow/pull/75062#issuecomment-6262058665
Carrying over the two review-body asks from #74696, which this PR was split out of. **Changelog** — added, as a `.. note::` directly under the `Changelog` header rather than under a version heading, following #74858, #73419 and #72057, so it doesn't have to guess the next version number. `_find_insertion_index_for_version` still returns `append=True` for `0.1.2` with the note in place, so the release tooling is unaffected. **Green 3.14 provider run** — done, locally against the Breeze 3.14 image: ``` platform linux -- Python 3.14.7, pytest-9.1.1 collected 73 items ======================== 73 passed, 1 warning in 23.11s ======================== ``` That first pass ran with the `pyvespa` the image already had (1.2.7), which is below the `>=1.2.9` this PR declares for 3.14, so it doesn't actually exercise the new floor. Re-running after upgrading to the declared floor: ``` Name: pyvespa Version: 1.2.9 ======================== 73 passed, 1 warning in 21.38s ======================== ``` 1.2.9 is the first release whose `requires-python` reaches past 3.14 (`<3.16`); every earlier release caps at `<3.14`, which is what the original exclusion in #74559 was working around. 3.11-3.13 stay on `pyvespa>=1.1.2` so nothing is forced to upgrade where the cap never bit. This PR's own CI 3.14 provider job now covers Vespa as well, since the provider is no longer in `excluded-python-versions`. --- Drafted-by: Claude Code (Opus 5) (no human review before posting) -- 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]
