potiuk opened a new pull request, #75333:
URL: https://github.com/apache/airflow/pull/75333

   Some `constraints-<VERSION>` tags contain constraints files for Python 
versions
   that the release's `requires-python` excludes. For example, Airflow 3.0.x 
ships
   `constraints-3.13.txt`. Those files pin packages without wheels for that
   interpreter (`grpcio==1.65.5` on 3.13), so users following the documented
   install command get a source build failure instead of a clear 404.
   
   `dev/remove_unsupported_python_constraints.py` finds these files and can 
remove them:
   
   - By default it only reports the affected tags and `constraints-X-Y` 
branches.
     It reads supported versions from `requires-python` when that has an upper
     bound, and otherwise from the trove classifiers, since classifiers lagged
     behind in several releases.
   - `--apply` commits the removal on top of each tagged commit and re-creates 
the
     tag there (GPG-signed by default). Branch fixes are commits on top of the 
branch tip.
   - `--push` force-pushes the re-created tags and fast-forwards the branches.
   
   Clear cases (excluded by `requires-python`): 3.0.0–3.0.6 (3.13), 3.1.0 (3.9),
   2.11.0–2.11.2 (3.8/3.9), 2.7.x (3.7). Older 2.x releases are flagged from
   classifiers only, so check the dry-run output before applying.
   
   Re-creating the tags replaces the original release managers' signatures. That
   should be agreed on dev@ before anyone runs `--push`.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Opus 5
   
   Generated-by: Claude Opus 5 following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to