Publish Airflow changes

For a plan, describe the steps without executing publication. For authorized publication, preserve existing approval and confirmation boundaries. Use the sections below for remote setup, existing PR checks, publication and issue tracking. Follow root AGENTS.md for the applicable test conventions and generated check commands; for contribution text, use Draft Airflow contribution text.

Git remote naming conventions

Airflow standardises on two git remote names, and the rest of this file, the contributing docs, and the release docs all assume them:

• upstream — the canonical apache/airflow repository (fetch from here).
• origin — the contributor's fork of apache/airflow (push PR branches here).