potiuk opened a new pull request, #75006:
URL: https://github.com/apache/airflow/pull/75006
The 2026-10-14 and 2026-10-17 providers waves ran into several steps that
`dev/README_RELEASE_PROVIDERS.md` doesn't cover. This PR writes them down:
- **Inter-provider pin floors:** `update-providers-next-version` only
resolves pins an author marked. A provider that starts importing a newer
`common.compat` symbol can ship with too low a floor, even when that provider
isn't in the wave (`openai` and `get_async_extra_dejson` this time). The doc
now has a recipe to find the first release that shipped a symbol, and the
`prepare-providers-documentation` skill now checks for this.
- **Tag the wave at an explicit commit:** the wave tag is created at
`${WAVE_SHA}` rather than at whatever `HEAD` is, and pushed through
`${APACHE_REMOTE}`, because the fresh build clone has only `origin`.
- **Re-cut before the vote email:** a new section. Keep the date, check that
nothing else touched the wave's providers, move the wave tag, rebuild from the
new commit, replace the SVN files (removing dropped ones), and publish the next
`rcN` with an explicit suffix.
- **`svn commit` needs your terminal:** without one (an agent session) it
fails with `E215004` instead of prompting.
- **Testing issue:** testers sometimes confirm a PR only in a comment. Tick
those in the previous issue before carrying the ticks over.
- **PyPI token without a terminal:** when an agent or script runs the
upload, `read -s` has nowhere to prompt. The doc points to Magpie's
`secret-prompt`, which asks in the terminal or a dialog and passes the token
only to `twine`. That needs apache/magpie#1696 to merge first, so the install
line works.
Docs only: the prek pre-commit and manual hooks pass on both files.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 5)
Generated-by: Claude Code (Opus 5) 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]
