potiuk opened a new pull request, #70955: URL: https://github.com/apache/airflow/pull/70955
Release commands enumerate providers from `generated/provider_dependencies.json`, filtering on each provider's `state`. `generate_provider_dependencies_if_needed()` runs on every breeze invocation, but its "json or sidecar missing" branch delegated to `get_provider_dependencies()`, which only regenerates when the json is **absent**. With the json present and the `.sha256sum` sidecar missing, the stale file was returned unchanged and no sidecar was ever written — so the staleness check stayed permanently disabled for that checkout. A provider whose `state` changed is then invisible to the release. `common.ai` was flipped to `ready` in 682cf06525, but a checkout carrying a json from before that still reported `not-ready`, so `breeze release-management prepare-provider-distributions` silently omitted `apache-airflow-providers-common-ai` 0.7.0 from the 2026-08-01 wave. It was caught only by an unrelated package-count mismatch during the RC cut. Both branches now force regeneration through a shared helper that removes the json first. The hash sidecar is also written only *after* regeneration succeeds, so a failed run no longer leaves a sidecar vouching for content that was never produced. Tests cover both broken paths (missing sidecar, and no sidecar written when regeneration raises); the up-to-date and stale-sidecar cases are guards that the shared-helper refactor did not change behaviour that already worked. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5) Generated-by: Claude Code (Opus 5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
