The GitHub Actions job "Tests" on airflow.git/fix-1305-wave-release-meta-token-expansion has failed. Run started by GitHub user kaxil (triggered by kaxil).
Head commit for run: ebc0f568ba222c8c06c4838f2ef6cdea9ad47e43 / Kaxil Naik <[email protected]> Fix wave-release auto-trigger meta-token expansion `publish-docs-to-s3.yml`'s build-info job dropped `all-providers` and `apache-airflow-providers` meta-tokens when computing `registry-providers`, which left the `update-registry` gate empty and silently skipped the registry update on every wave release. This fix extracts the registry-trigger logic into a small, unit-tested Python script (`dev/registry/derive_wave_providers.py`). When `INCLUDE_DOCS` contains a meta-token (`all`, `all-providers`, `apache-airflow-providers`) AND the dispatch ref matches the wave-tag pattern (`providers/YYYY-MM-DD`), the script derives the wave's actual provider list from per-provider tags reachable from the wave ref but not from the previous wave tag. Only those providers go through the incremental registry build; non-wave providers' download counts and latest pointers stay untouched. For non-wave-tag dispatches (e.g., manual rebuild against `main`) or when the derivation produces an empty list, the script falls back to a full registry rebuild via a new `registry-full-build` output, which the gate honors alongside the existing per-provider list. The downstream `registry-build.yml` already interprets `provider: ""` as "full build", so no change is needed there. Report URL: https://github.com/apache/airflow/actions/runs/25126926318 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
