shahar1 opened a new pull request, #74098: URL: https://github.com/apache/airflow/pull/74098
When releasing ad-hoc, using `breeze release-management update-providers-next-version` rewrites every `# use next version` to the referenced provider's current 'provider.yaml', without considering whether this version is actually being released as part of the ad-hoc. This PR should fix it by checking if its current version is already released, so "next version" refers to a future release. <details><summary>AI Summary</summary> `breeze release-management update-providers-next-version` rewrote every `# use next version` pin to the referenced provider's current `provider.yaml` version and dropped the marker, without checking that this version is the one being released. That is correct in a regular wave, where the referenced provider is bumped in the same PR. In an ad-hoc release that does not include the referenced provider, its current version is already released, so "next version" means a future release. Resolving the pin then produced a floor that admits a release lacking the required code, and losing the marker meant later waves never corrected it. Observed during the 2026-10-02 ad-hoc release (cncf.kubernetes, edge3, duckdb): common.compat 1.20.0 was tagged 2026-09-24, and the `# use next version` pins added on 2026-10-01 by #73967 (anthropic) and #73991 (common.ai) were rewritten to `>=1.20.0`. The command now leaves a pin untouched when the referenced provider's current version has a final release tag. Release candidate tags alone are ambiguous (the version is either in vote or being re-cut in this very release), so the pin is still resolved in that case, with a warning telling the release manager to revert it if the provider is not part of the release. Pins to a version with no tag resolve exactly as before. Checks run: `pytest dev/breeze/tests/test_packages.py -k next_version` (3 passed: no tag, final tag, rc tags only), `prek run --files` on the four changed files (clean), and the command itself from this branch, which now skips all four pending pins and changes no `pyproject.toml`. </details> --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Fable 5.1) Generated-by: Claude Code (Fable 5.1) 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]
