pierrejeambrun opened a new pull request, #68760: URL: https://github.com/apache/airflow/pull/68760
Custom operator and TaskGroup colors were dropped in Airflow 3 — the `ui_color` / `ui_fgcolor` attributes were kept on operators and task groups but the new UI ignored them. This reintroduces the coloring in a way that fits the new opinionated light/dark theming. The value must now be a **Chakra palette token** (e.g. `blue.500`, `purple.600`, or any token a deployment adds through custom theming). A token resolves through a theme-controlled CSS variable, so it stays legible in both light and dark mode — addressing the dark-mode / accessibility concerns that drove the original removal. The graph paints the node **fill** from `ui_color` and the **operator label** from `ui_fgcolor` (as in Airflow 2.x), while the border keeps showing run state. Legacy hex / CSS-name values (e.g. `#e8b7e4`) can't adapt to the theme, so they are ignored by the graph and emit a parse-time warning for **user-authored** operators and task groups (built-in operators and providers stay silent). closes: #54474 ##### Graph (light) - _screenshot: graph-light_ ##### Graph (dark) - _screenshot: graph-dark_ --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 4.8) Generated-by: Claude Code (Opus 4.8) 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]
