Skip to content

Fix provider registry never updating after docs publish#65188

Merged
potiuk merged 1 commit intoapache:mainfrom
astronomer:fix-registry-update-on-docs-publish
Apr 14, 2026
Merged

Fix provider registry never updating after docs publish#65188
potiuk merged 1 commit intoapache:mainfrom
astronomer:fix-registry-update-on-docs-publish

Conversation

@kaxil
Copy link
Copy Markdown
Member

@kaxil kaxil commented Apr 14, 2026

The "Update Provider Registry" job in publish-docs-to-s3.yml has never actually run. Every docs publish since the registry integration was added has skipped it.

The include-docs workflow 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-providers was always empty and the job was always skipped.

Past registry updates succeeded only through manual registry-build.yml dispatches.

Fix

Handle both input formats:

  • Full package names: strip apache-airflow-providers- prefix (existing behavior)
  • Short names: convert dots to hyphens (common.ai -> common-ai)
  • Non-provider packages (apache-airflow, helm-chart, etc.): skip

Verified with the April 13 input (common.compat amazon openlineage common.ai) -- all four now correctly produce registry provider IDs.

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.
@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch labels Apr 14, 2026
Copy link
Copy Markdown
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah good catch!

@potiuk potiuk merged commit 01354a4 into apache:main Apr 14, 2026
142 checks passed
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>
@github-actions
Copy link
Copy Markdown

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-2-test PR Link

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants