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

   The README quickstart on `main` still installs `apache-airflow==3.3.0` 
although 3.3.2 was released (2026-09-17) and the constraints branch 
`constraints-3.3.2` exists (verified HTTP 200). The 3.3.2 release commit 
(bf973cb) updated the lifecycle table row but the installation section and the 
"Stable version" header in Requirements were missed.
   
   This PR updates the five pin sites found by 
[auroraxo/docrot](https://github.com/auroraxo/docrot)'s version-drift scanner 
and verified line by line:
   
   - line 104: `Stable version (3.3.0)` → `Stable version (3.3.2)` 
(Requirements table header)
   - lines 177-178: quickstart `pip install` pin + constraint URL
   - lines 184-185: extras example pin + constraint URL
   
   No other `3.3.0` occurrences are touched. Markdown structure unchanged (no 
headings, no top-of-file bytes), so doctoc/insert-license hooks are unaffected.
   
   closes: #73769
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes - Claude (via OpenClaw autonomous agent "Aurora")
   
   Generated-by: Claude following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an AIP is not needed for this docs-only 
change.
   * No dependency added, no user-facing behavior change, so no newsfragment 
required.
   


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