o-nikolas opened a new pull request, #72168:
URL: https://github.com/apache/airflow/pull/72168

   The testing-status issue title is `Status of testing Providers that were 
prepared on <date>`, where the date identifies the wave. `breeze 
release-management generate-issue-content-providers` always generated it from 
`datetime.now()`, so the title reflects when the issue happened to be created 
rather than the wave the release manager tagged, built, signed and voted on. 
The two diverge whenever issue creation slips past midnight, or a wave is 
re-cut and the issue regenerated a day later.
   
   `RELEASE_DATE` is already the canonical wave identifier and is already 
consumed as an `envvar` by other release commands 
(`prepare-provider-documentation`, `tag-providers`), so this adds a 
`--release-date` option in the same shape — same `validate_release_date` 
callback, same `YYYY-MM-DD[_NN]` format — and falls back to today when it is 
unset, keeping current behaviour for anyone not exporting it.
   
   **Tested:** new parametrized tests for `_get_prepared_on_date` covering a 
plain date, the `_NN` wave suffix, and the unset/empty fallback; all 51 tests 
in `dev/breeze/tests/test_release_management_commands.py` pass. The regenerated 
breeze command image/txt are included (the `update-breeze-cmd-output` hook), 
and `prek run --from-ref upstream/main --stage pre-commit` is clean.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Kiro CLI (claude-fable-5)
   
   Generated-by: Kiro CLI (claude-fable-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]

Reply via email to