potiuk opened a new pull request, #67078:
URL: https://github.com/apache/airflow/pull/67078

   Backport of #66255 to `v3-2-test`.
   
   Brings in `run_gh_command` / `retrieve_github_token` helpers so Breeze 
prefers a user's stored `gh auth login` credential over ambient `GH_TOKEN` / 
`GITHUB_TOKEN` env vars (with a retry against env tokens when the clean-env 
attempt fails).
   
   Also fixes a pre-existing latent break on `v3-2-test`: the earlier backport 
#66776 referenced `run_gh_command` in 
`dev/breeze/src/airflow_breeze/commands/workflow_commands.py` but its 
prerequisite (this PR) had never been cherry-picked, leaving `mypy-dev` failing 
on `v3-2-test`. With this backport, the import resolves and mypy is green again.
   
   Conflicts during cherry-pick:
   - `dev/breeze/src/airflow_breeze/utils/github.py` — kept both the existing 
`dataclass, field` import (still used by `PRAssessment` / `Violation`) and the 
new `Mapping, Sequence` import introduced by #66255.
   - `dev/breeze/src/airflow_breeze/commands/release_management_commands.py` — 
left the airflow-ctl changelog block (`_get_airflowctl_prs`, 
`generate_airflowctl_changelog`, etc.) out, since that feature isn't on 
`v3-2-test` and #66255 doesn't introduce it. Applied the 
`retrieve_github_token(github_token) or ""` line in `generate_issue_content`.
   - `dev/breeze/doc/images/output_*.{svg,txt}` — regenerated via `breeze setup 
regenerate-command-images --force` so they reflect v3-2-test's actual command 
set (not main's).
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.7)
   
   Generated-by: Claude Code (Opus 4.7) 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