potiuk commented on issue #72902:
URL: https://github.com/apache/airflow/issues/72902#issuecomment-5652110795
Verified the 2026-09-09 RC (38 providers) end to end — all checks pass.
**Artifacts** (`dist/dev/airflow/providers/2026-09-09`): folder complete
(231 files = 38×6 + source trio; 77 `.sha512` / 77 `.asc`, no double-extension
leftovers); SHA512 **77/77**; GPG **77/77** good, all on the RM's key
`1E7A857875E0EE49DB99E4431B17D6C5938CED00` (in KEYS); **reproducible build
77/77 byte-identical** — 76 wheels+sdists rebuilt from tag
`providers/2026-09-09` (`209e34c5022a78c7691ac68a50f60d976242e17d`), plus the
source tarball; Apache RAT 0.18 — **0 unapproved / 0 unknown** (10146 standard
files, all AL2.0).
**Consistency**: all 38 rc tags point at the wave commit; 38/38
`pyproject.toml` versions match their changelog tops; 38/38 PyPI rc pages
resolve with both wheel and sdist.
**My own changes in this wave** — ticked above. Each was confirmed present
in the shipped wheel, not just at the tag, and its tests run green:
| PR | Provider | Tests |
|---|---|---|
| #72646 | akeyless 0.3.1 | 37 passed |
| #72645, #72657, #72198, #72199 | fab 3.9.0 | 281 passed |
| #72207, #72205 | keycloak 0.10.0 | 202 passed, 1 skipped |
For #72646 I also exercised the namespace guard from a clean venv containing
only the RC wheel: a cross-team key under multi-team + team-scoped path is
refused, while a flat key, `use_team_secrets_path=False`, an absent team name,
and multi-team disabled all still resolve.
**One non-blocking observation** (pre-existing, unchanged since the
2026-08-18 wave): the source tarball ships two OFL-1.1 web fonts at
`registry/public/fonts/{jetbrains-mono-latin,plus-jakarta-sans-latin}.woff2`
while the root `LICENSE` is bare AL2.0 with no third-party section. Confirmed
this wave that they are **source-tarball only** — no provider wheel contains
them. A LICENSE follow-up, not a re-cut.
---
Drafted-by: Claude Opus 5; reviewed by @potiuk before posting
--
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]
