Cool. Thanks for the clarification, I just merged my PR now. Thanks & Regards, Amogh Desai
On Thu, Nov 5, 2026 at 8:43 AM Jarek Potiuk <[email protected]> wrote: > Yes. That is just fixing a missing dependency. We already do it for > providers + airflow - i.e. selective checks automatically detects which of > the "components" is affected - for example when you modify google provider > only, any other provider that imports google (say amazon that has some > google provider imports) are automatically added as "affected" and both -> > tests and docs are built for both. Additionally - it also tries to build > the docs up to 3 times -> because they are built in parallelncl, and there > might be different cross-dependencies, and when you add a new "anchor" in > one provider that is used in another, it could be that the "dependent" > provider is still being build (and old inventory of links it provides as > sphinx module does not have the new anchor). So we try to build things > three times - every time removing from the "affected" list the components > that completed successfully (because when they do - other providers using > them will use the newly build docs as source of the inventory links :) . > > J. > > On Wed, Nov 4, 2026 at 5:34 AM Amogh Desai via dev <[email protected]> > wrote: > >> Hi all, >> >> I noticed today that the docs build broke for PRs that only touch airflow >> core. >> >> Why? #75405 added a new task SDK docs page and linked to it from the core >> docs. That PR passed because CI built both doc sets. >> But when a PR only touches core, CI builds only the core docs (I didn't >> trace back why, but it doesn't seem right). It checks task SDK >> links against the published site. The new page is not published yet, so >> the >> link fails. #76376 is an example where we hit this. >> >> Airflow core and the task SDK release together (until today), so this will >> happen again whenever one of them links to something on the other. >> >> I propose that we always build both doc sets when either one changes. The >> task SDK docs are small, so this adds little time. I have a PR >> in progress here: https://github.com/apache/airflow/pull/76443. >> >> Just checking in to see if anyone has any concerns / thoughts / feedback. >> >> >> Thanks & Regards, >> Amogh Desai >> >
