Fix provider registry never updating after docs publish#65188
Merged
potiuk merged 1 commit intoapache:mainfrom Apr 14, 2026
Merged
Fix provider registry never updating after docs publish#65188potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
The include-docs input uses short provider names like "amazon" and "common.ai", but the extraction logic only matched full package names like "apache-airflow-providers-amazon". This meant REGISTRY_PROVIDERS was always empty and the registry update job was always skipped. Handle both short names (converting dots to hyphens) and full package names, while skipping non-provider packages.
eladkal
approved these changes
Apr 14, 2026
potiuk
approved these changes
Apr 14, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Apr 14, 2026
…65188) The include-docs input uses short provider names like "amazon" and "common.ai", but the extraction logic only matched full package names like "apache-airflow-providers-amazon". This meant REGISTRY_PROVIDERS was always empty and the registry update job was always skipped. Handle both short names (converting dots to hyphens) and full package names, while skipping non-provider packages. (cherry picked from commit 01354a4) Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
Backport successfully created: v3-2-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
Apr 14, 2026
…pache#65188) The include-docs input uses short provider names like "amazon" and "common.ai", but the extraction logic only matched full package names like "apache-airflow-providers-amazon". This meant REGISTRY_PROVIDERS was always empty and the registry update job was always skipped. Handle both short names (converting dots to hyphens) and full package names, while skipping non-provider packages. (cherry picked from commit 01354a4) Co-authored-by: Kaxil Naik <kaxilnaik@gmail.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 "Update Provider Registry" job in
publish-docs-to-s3.ymlhas never actually run. Every docs publish since the registry integration was added has skipped it.The
include-docsworkflow input uses short provider names (amazon,common.ai,openlineage), but the extraction logic only matched full package names (apache-airflow-providers-amazon). Since nothing matched,registry-providerswas always empty and the job was always skipped.Past registry updates succeeded only through manual
registry-build.ymldispatches.Fix
Handle both input formats:
apache-airflow-providers-prefix (existing behavior)common.ai->common-ai)apache-airflow,helm-chart, etc.): skipVerified with the April 13 input (
common.compat amazon openlineage common.ai) -- all four now correctly produce registry provider IDs.