Dattuog opened a new pull request, #73741: URL: https://github.com/apache/airflow/pull/73741
DAG tags are limited to 100 characters per individual tag because each tag is stored in the metadata database's `dag_tag.name` column. There is no combined-length restriction. This updates the existing validation error to identify the first offending tag with a bounded preview and report its actual length and the configured limit. The accepted and rejected input set is unchanged. Regression coverage confirms that: - a tag of exactly 100 characters is accepted - a 101-character tag is rejected with useful diagnostic information - multiple tags whose combined length exceeds 100 remain valid when each individual tag is within the limit closes: #55693 ### Testing Passed: - `uv run --no-sync ruff format --check task-sdk/src/airflow/sdk/definitions/dag.py task-sdk/tests/task_sdk/definitions/test_dag.py` - `uv run --no-sync ruff check task-sdk/src/airflow/sdk/definitions/dag.py task-sdk/tests/task_sdk/definitions/test_dag.py` - `uvx --from prek prek run ruff --files task-sdk/src/airflow/sdk/definitions/dag.py task-sdk/tests/task_sdk/definitions/test_dag.py` - `uvx --from prek prek run check-no-new-airflow-exceptions --files task-sdk/src/airflow/sdk/definitions/dag.py task-sdk/tests/task_sdk/definitions/test_dag.py` - `uv run --no-sync python -m py_compile task-sdk/src/airflow/sdk/definitions/dag.py task-sdk/tests/task_sdk/definitions/test_dag.py` - `git diff --check` The focused pytest run could not collect on native Windows because repository symlinks such as `airflow._shared.configuration` are represented as ordinary placeholder files. It should be run in Linux, WSL, or Breeze; pytest is not claimed as passing locally. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (OpenAI Codex) Generated-by: OpenAI Codex 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]
