Repository navigation
Record lessons from the October 2026 providers waves in the release docs - #75006
Merged
Merged
Conversation
The 2026-10-14 and 2026-10-17 waves hit steps the instructions did not cover: a provider outside the wave shipping with a common.compat floor below the first release that has the symbol it imports, a candidate that had to be rebuilt before its vote email went out, a build clone with no upstream remote, an svn commit that cannot prompt from an agent session, tester confirmations that only lived in issue comments, and a PyPI token prompt that needs a terminal an agent does not have. Generated-by: Claude Opus 5
potiuk
requested review from
bugraoz93,
jedcunningham,
jscheffl,
shahar1 and
vincbeck
as code owners
October 18, 2026 15:26
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-4-test
shahar1
approved these changes
Oct 18, 2026
Contributor
Backport successfully created: v3-4-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Oct 18, 2026
…he release docs (apache#75006) The 2026-10-14 and 2026-10-17 waves hit steps the instructions did not cover: a provider outside the wave shipping with a common.compat floor below the first release that has the symbol it imports, a candidate that had to be rebuilt before its vote email went out, a build clone with no upstream remote, an svn commit that cannot prompt from an agent session, tester confirmations that only lived in issue comments, and a PyPI token prompt that needs a terminal an agent does not have. (cherry picked from commit 986066e) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Generated-by: Claude Opus 5
aws-airflow-bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Oct 18, 2026
…he release docs (apache#75006) The 2026-10-14 and 2026-10-17 waves hit steps the instructions did not cover: a provider outside the wave shipping with a common.compat floor below the first release that has the symbol it imports, a candidate that had to be rebuilt before its vote email went out, a build clone with no upstream remote, an svn commit that cannot prompt from an agent session, tester confirmations that only lived in issue comments, and a PyPI token prompt that needs a terminal an agent does not have. (cherry picked from commit 986066e) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Generated-by: Claude Opus 5
potiuk
added a commit
that referenced
this pull request
Oct 18, 2026
…he release docs (#75006) (#75008) The 2026-10-14 and 2026-10-17 waves hit steps the instructions did not cover: a provider outside the wave shipping with a common.compat floor below the first release that has the symbol it imports, a candidate that had to be rebuilt before its vote email went out, a build clone with no upstream remote, an svn commit that cannot prompt from an agent session, tester confirmations that only lived in issue comments, and a PyPI token prompt that needs a terminal an agent does not have. (cherry picked from commit 986066e) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Oct 20, 2026
…he release docs (#75006) (#75008) The 2026-10-14 and 2026-10-17 waves hit steps the instructions did not cover: a provider outside the wave shipping with a common.compat floor below the first release that has the symbol it imports, a candidate that had to be rebuilt before its vote email went out, a build clone with no upstream remote, an svn commit that cannot prompt from an agent session, tester confirmations that only lived in issue comments, and a PyPI token prompt that needs a terminal an agent does not have. (cherry picked from commit 986066e) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 2026-10-14 and 2026-10-17 providers waves ran into several steps that
dev/README_RELEASE_PROVIDERS.mddoesn't cover. This PR writes them down:update-providers-next-versiononly resolves pins an author marked. A provider that starts importing a newercommon.compatsymbol can ship with too low a floor, even when that provider isn't in the wave (openaiandget_async_extra_dejsonthis time). The doc now has a recipe to find the first release that shipped a symbol, and theprepare-providers-documentationskill now checks for this.${WAVE_SHA}rather than at whateverHEADis, and pushed through${APACHE_REMOTE}, because the fresh build clone has onlyorigin.rcNwith an explicit suffix.svn commitneeds your terminal: without one (an agent session) it fails withE215004instead of prompting.read -shas nowhere to prompt. The doc points to Magpie'ssecret-prompt, which asks in the terminal or a dialog and passes the token only totwine. That needs feat(secret-prompt): ask the release manager for an upload token without exposing it 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?
Generated-by: Claude Code (Opus 5) following the guidelines