Skip to content

Update Python Client to 3.2.2#155

Merged
vatsrahul1001 merged 1 commit into
mainfrom
release-3.2.2
Jun 1, 2026
Merged

Update Python Client to 3.2.2#155
vatsrahul1001 merged 1 commit into
mainfrom
release-3.2.2

Conversation

@vatsrahul1001
Copy link
Copy Markdown
Contributor

No description provided.

@vatsrahul1001 vatsrahul1001 changed the title Update Python Client to 3.2.2rc2 Update Python Client to 3.2.2 Jun 1, 2026
@vatsrahul1001 vatsrahul1001 requested review from ephraimbuddy, kaxil, pierrejeambrun and potiuk and removed request for kaxil June 1, 2026 09:57
@vatsrahul1001 vatsrahul1001 merged commit 3054e29 into main Jun 1, 2026
1 check passed
Copy link
Copy Markdown
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified the generated client is reproducible from the committed spec/v2.yaml — nothing was hand-edited; the whole airflow_client/client/ and test/ trees regenerate byte-for-byte (after the trigger_dag_run_post_body AST patch under Python 3.10). LGTM.

One thing to flag for the toolchain (not blocking this PR): this was generated with openapi-generator-cli v7.22.0, but apache/airflow's breeze currently pins v7.21.0. With 7.21.0, three files diverge (api_client.py, configuration.py, connection_body.py — newer-generator codegen for sanitize_for_serialization, the retries type, and validator coercion). 3.2.1 matched 7.21.0, so the generator drifted between releases. I'm bumping breeze's pin to 7.22.0 so future regenerations stay self-consistent.

Minor, harmless: docs/DAGRunApi.md keeps its 3.2.1-era casing while the generator now emits DagRunApi.md (content identical) — a case-only rename dropped on a case-insensitive (macOS) filesystem. Worth a follow-up git mv so it matches canonical output, but it doesn't affect the importable package.


Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting

@potiuk
Copy link
Copy Markdown
Member

potiuk commented Jun 1, 2026

Correction to my review above: I checked against a slightly stale apache/airflow checkout. breeze on main has already pinned openapi-generator-cli to 7.22.0 since #66068 (2026-05-04), which is exactly the version this PR was generated with — so the toolchain and the release are in sync and there's nothing to bump. The reproducibility verdict is unchanged: the client regenerates byte-for-byte from the committed spec/v2.yaml with 7.22.0. Apologies for the noise.


Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants