github-actions[bot] opened a new pull request, #76022:
URL: https://github.com/apache/airflow/pull/76022

   An incremental registry build downloads the bucket's providers.json and
   modules.json, merges its own providers in and syncs them back. Docs
   publishes call it, release managers fire subset and fix-up publishes,
   and the backfill writes the same bucket, so two of them overlapping
   silently drop whichever finished first from the registry index.
   
   Docs publishes to one bucket and the two constraints publishers had the
   same exposure in smaller form. Provider and Airflow docs land in
   different paths, so those two kinds of docs sync keep running side by
   side. The packages-metadata.json they both rewrite from a scan of the
   whole bucket moves to its own job, serialised per bucket, using new
   --skip-packages-metadata and --packages-metadata-only flags of
   publish-docs-to-s3. The Docker Hub release grouped on the bare version
   string, which any other workflow using a version as its group would
   collide with.
   (cherry picked from commit c6a077b0efe7520d3e58dd7a5477a74ff14a4ba6)
   
   Co-authored-by: Jarek Potiuk <[email protected]>
   Generated-by: Claude Opus 5


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