Skip to content

Change v1 to v2 in generated OpenAPI schema files - #50705

Merged
kaxil merged 1 commit into
apache:mainfrom
astronomer:change-v1-to-v2
May 17, 2025
Merged

Change v1 to v2 in generated OpenAPI schema files#50705
kaxil merged 1 commit into
apache:mainfrom
astronomer:change-v1-to-v2

Conversation

@kaxil

@kaxil kaxil commented May 16, 2025

Copy link
Copy Markdown
Member

(depends on #50704)

To remove confusion with APIv1, let's align filesnames too.


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@bugraoz93 bugraoz93 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks, Kaxil! Make sense!

@kaxil
kaxil force-pushed the change-v1-to-v2 branch 2 times, most recently from 3dd8d44 to ff54906 Compare May 16, 2025 23:39
To remove confusion with APIv1, let's align filesnames too.
@kaxil
kaxil force-pushed the change-v1-to-v2 branch from ff54906 to 6bdb794 Compare May 16, 2025 23:54
@kaxil
kaxil merged commit baf5fae into apache:main May 17, 2025
@kaxil
kaxil deleted the change-v1-to-v2 branch May 17, 2025 08:05
@potiuk potiuk modified the milestone: Airflow 3.0.2 May 21, 2025
@potiuk

potiuk commented May 21, 2025

Copy link
Copy Markdown
Member

Question @kaxil -> is this one airflow 3.1 or Airflow 3.0.* cherry-pickable ?

@kaxil

kaxil commented May 21, 2025

Copy link
Copy Markdown
Member Author

baf5fae

cherry-pickale but have to deal with some conflicts so didn't do. No user impact so can go in 3.1 too

@potiuk

potiuk commented May 21, 2025

Copy link
Copy Markdown
Member

baf5fae

cherry-pickale but have to deal with some conflicts so didn't do. No user impact so can go in 3.1 too

Ack. I had a conflct in #50886 so I left v1 in v3-0-test.

sanederchik pushed a commit to sanederchik/airflow that referenced this pull request Jun 7, 2025
kaxil added a commit that referenced this pull request Jun 10, 2025
@kaxil kaxil added this to the Airflow 3.0.3 milestone Jun 10, 2025
shahar1 added a commit to shahar1/airflow that referenced this pull request Jul 29, 2026
apache#68919 changed _private_ui.yaml without regenerating the TypeScript client
and CI stayed green: selective checks decide whether to skip the
ts-compile-lint-* hooks from file groups that do not cover the UI codegen
input specs, while the hooks themselves trigger on any yaml under the
openapi directories. The stale client then masked a type error that broke
main for every PR running full static checks. The same gap applied to
v2-simple-auth-manager-generated.yaml, so a spec-only change also skipped
the simple auth manager UI hook. Track the codegen-input specs in their own
file group so spec-only changes run the UI hooks without forcing the full
test matrix, and drop the main UI hook trigger for the simple auth manager
spec: that pattern was copied in when the hook was created (apache#51725), a
month after the spec was renamed v1 to v2 (apache#50705), so it has never matched
a file - apache#53636 fixed the sibling hook's copy but missed this one. The main
UI codegen does not consume that spec either.
pierrejeambrun pushed a commit that referenced this pull request Jul 29, 2026
#68919 changed _private_ui.yaml without regenerating the TypeScript client
and CI stayed green: selective checks decide whether to skip the
ts-compile-lint-* hooks from file groups that do not cover the UI codegen
input specs, while the hooks themselves trigger on any yaml under the
openapi directories. The stale client then masked a type error that broke
main for every PR running full static checks. The same gap applied to
v2-simple-auth-manager-generated.yaml, so a spec-only change also skipped
the simple auth manager UI hook. Track the codegen-input specs in their own
file group so spec-only changes run the UI hooks without forcing the full
test matrix, and drop the main UI hook trigger for the simple auth manager
spec: that pattern was copied in when the hook was created (#51725), a
month after the spec was renamed v1 to v2 (#50705), so it has never matched
a file - #53636 fixed the sibling hook's copy but missed this one. The main
UI codegen does not consume that spec either.
potiuk pushed a commit that referenced this pull request Jul 30, 2026
…nges (#70643)

#68919 changed _private_ui.yaml without regenerating the TypeScript client
and CI stayed green: selective checks decide whether to skip the
ts-compile-lint-* hooks from file groups that do not cover the UI codegen
input specs, while the hooks themselves trigger on any yaml under the
openapi directories. The stale client then masked a type error that broke
main for every PR running full static checks. The same gap applied to
v2-simple-auth-manager-generated.yaml, so a spec-only change also skipped
the simple auth manager UI hook. Track the codegen-input specs in their own
file group so spec-only changes run the UI hooks without forcing the full
test matrix, and drop the main UI hook trigger for the simple auth manager
spec: that pattern was copied in when the hook was created (#51725), a
month after the spec was renamed v1 to v2 (#50705), so it has never matched
a file - #53636 fixed the sibling hook's copy but missed this one. The main
UI codegen does not consume that spec either.
(cherry picked from commit b43a87e)

Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants