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

   ## Human Summary
   
   Adopts rc-verify skill for provider's verification - adding Airflow-specific 
override which allows
   to automatically test your own changes - by generating Dag covering the 
changes with mocked
   external dependencies where applicable.
   
   ## AI Summary
   
   <details><summary>Click here</summary>
   
   Contributors are asked to test their changes in every providers wave, but 
finding the right
   distributions, installing the whole wave together and building a 
reproduction for each change
   is tedious enough that it is often skipped. This adopts Apache Magpie's 
release-management
   family and adds an Airflow override that lets an agent do the mechanical 
part:
   
   * `.apache-magpie-overrides/release-verify-rc.md` — an optional step for the 
`verify-rc` skill:
     find the user's checkboxes in the "Status of testing Providers" issue (and 
their PRs that are
     in the wave but missing from it), verify each change is in the RC tag, the 
changelog and the
     PyPI wheel, download the whole wave into `dist/`, write a mock-based 
verification Dag with one
     task per change, and hand over the `breeze start-airflow 
--use-distributions-from-dist`
     command. Ticking boxes and commenting on the issue only happen after the 
user confirms.
   * `.apache-magpie.lock` — `magpie-release-management` added to the project 
floor
     (`min_version` raised to the version the skills were checked against).
   * `release-management-config.md` / `release-build.md` — project 
configuration for the
     **providers train only**, taken from `dev/README_RELEASE_PROVIDERS.md`; 
other trains,
     `pmc-roster.md` and `release-trains.md` are left for a follow-up.
   * `project.md`, `AGENTS.md`, `README.md` — pointers and install notes.
   
   The `.claude/settings.json` wiring from magpie's adopt step is intentionally 
not added — the
   existing `setup-isolated-setup-install` override notes that committing that 
file is a separate
   project-level decision.
   
   The flow was dog-fooded on the 2026-09-22 providers wave (#73658): 7 changes 
across 7 providers
   verified in tags, changelogs and wheels, and tested with all 78 RC providers 
installed from
   files in Breeze.
   
   Verification: `prek` pre-commit hooks pass (including the lychee link 
check); the skill-eval
   passed 12/12 and `dev/skill-evals/last-eval-hash.txt` is updated.
   
   </details>
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5.5)
   
   Generated-by: Claude Code (Opus 5.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