vatsrahul1001 opened a new pull request, #73056:
URL: https://github.com/apache/airflow/pull/73056

   #73042 bumped ruff (`0.15.17`->`0.16.6`) and mypy (`2.1.0`->`2.3.1`) on 
`v3-3-test`, but not the companion config/fixes that keep static checks green — 
those live in separate `main` PRs. As a result, the 3.3.2 sync PR #72946 (which 
runs `prek --all-files` against the full diff vs stable) fails across **ruff**, 
**ruff-format**, **mypy**, and **zizmor**.
   
   Root cause: without the pinned base lint rule set, ruff 0.16 falls back to 
its widened default (~510 rules) and reports **6278 errors**; its `B010` 
autofix rewrites the `setattr` calls on the fake modules in the devel-common 
tests, which then trips mypy's `attr-defined` check. Pinning the base set 
clears both at once.
   
   **Changes (each mirrors main unless noted):**
   - `pyproject.toml`: pin the ruff base rule set `select = ["E4", "E7", "E9", 
"F"]` and defer `ISC004`/`LOG004` — from #70725. Collapses 6278 -> 0.
   - `.github/zizmor.yml`: disable the `self-repository` audit — from main's 
config.
   - `.github/workflows/run-unit-tests.yml` + `publish-docs-to-s3.yml`: rewrite 
unsound ternaries to `case(...)` — backport of #69026.
   - `shared/.../plugins_manager.py`: `# type: ignore[attr-defined]` on the 
name-validated `AirflowPlugin.validate()` call (local — this code was 
refactored away on main, so no backport exists).
   - `task-sdk/.../schema/AGENTS.md`: ruff-format a doc code snippet.
   
   This is the companion migration that should have accompanied #73042's 
toolchain bump; it unblocks the 3.3.2rc1 sync PR #72946.
   
   ##### 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]

Reply via email to