shahar1 opened a new pull request, #77286: URL: https://github.com/apache/airflow/pull/77286
Manual backport of #77211 to `v3-4-test`. The automatic backport failed. This PR is stacked on the backport of #74764, which #77211 depends on. On `main`, #77211 also relies on #76567 (Triggers page). #76567 is not being backported, so the conflicts were resolved for `v3-4-test` as follows: - `router.tsx`: `v3-4-test` still registers routes eagerly instead of through `lazyRoute`. The Partitions route is added in the eager style. - OpenAPI spec and generated UI client: regenerated. `DagRunAssetReference` is still a `StrictBaseModel` on `v3-4-test`, so the private UI spec now marks it `additionalProperties: false`, the same as the public spec. Without that, the client generator emits a duplicate `DagRunAssetReference1` type. - `AssetPartitions.test.tsx`: without #76567, the multiselect filter pill shows the raw selected values (`failed, in_progress`) rather than their labels. One assertion is adjusted to match. The other state filters on this branch behave the same way. - `AssetPartitions.tsx`: one ternary is rewritten as `&&` with the same behaviour, to satisfy the ESLint rule set on `v3-4-test`. Checks run locally: - `pytest airflow-core/tests/unit/api_fastapi/core_api/routes/ui/test_assets.py` (SQLite): 90 passed. - `vitest` for `src/pages/Asset`, `src/pages/Dag/Backfills`, `src/pages/DagsList/DagsFilters` and `src/pages/TaskInstances`: all pass after the test adjustment. - `prek run --stage pre-commit` on both commits: passed. The `generate-openapi-spec` hook could not build the Breeze image here, so the same generator script was run through `uv` instead. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5.5) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
