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

   Cherry-pick of #63288 for the Airflow 3.2.2 patch release.
   
   Backported as a prerequisite for the \`breeze registry\` tooling chain that 
ultimately enables #66311 (Breeze \`down\` discovery). #63288 introduces the 
\`@option_python\` decorator on \`registry backfill\` and the parallel-backfill 
plumbing that downstream PRs (#65223, #65972, #65984, #66311) build on.
   
   ### Conflict resolution
   
   - \`dev/registry/extract_connections.py\`, 
\`dev/registry/extract_parameters.py\`, 
\`dev/breeze/src/airflow_breeze/commands/registry_commands.py\`: PR makes 
substantive content changes that didn't auto-merge against v3-2-test's older 
shapes. Took PR side wholesale via \`git checkout --theirs\` for these files — 
they're being rewritten to support parallel backfill, so taking PR side is the 
right call.
   - \`dev/breeze/doc/images/output_registry{,_backfill}.{svg,txt}\`: 
auto-generated CLI help output; regenerated by the \`Update breeze docs\` prek 
hook during commit.
   
   ### Lint fix-up
   
   \`Run mypy for dev\` flagged a \`redundant-cast\` on 
\`extract_parameters.py:569\`:
   
   \`\`\`python
   cls = typing.cast("type[typing.Any]", candidate)  # redundant
   \`\`\`
   
   Replaced with \`cls = candidate\` — \`candidate\` is already narrowed by 
\`inspect.isclass(candidate)\` immediately above, so the cast was redundant.
   
   ---
   
   ##### 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