The GitHub Actions job "Tests (AMD)" on airflow.git/ruff-0-16-upgrade has 
failed.
Run started by GitHub user Lee-W (triggered by Lee-W).

Head commit for run:
a9ba3babb992f9668a68794583119c538f9febd2 / Wei Lee <[email protected]>
Bump ruff to 0.16.0 and pin the base lint rule set

Ruff 0.16 widened its default rule set from ~250 to ~510 enabled rules.
Airflow's config uses extend-select, which layers on top of whatever Ruff
currently enables by default, so the bump would have silently pulled in 261
unreviewed rules and produced sweeping autofix churn across the repo. Pin
`select` to the rule groups Airflow has always effectively had enabled, so
future Ruff releases cannot change our lint surface out from under us;
everything intentionally on is still listed in extend-select as before.

Two rules remain newly in scope under the pin, because they sit inside
sections Airflow selects wholesale. Both are deferred behind `ignore` rather
than fixed here: a version bump should not also carry semantic changes, and
both need per-site judgement that deserves its own reviewed change. ISC004's
autofix is unsafe, and LOG004's call sites can only be classified by tracing
whether an exception is genuinely in flight at each one.

Ruff 0.16 also started formatting Python blocks inside Markdown, which is why
a task-sdk doc changes alongside the bump rather than in its own commit: its
example was a bare statement that the formatter rewrites into a one-element
tuple, which would have changed what the example teaches. Showing the entry
in its surrounding context keeps it both correct and stable to format.

The lockfile additionally picks up datamodel-code-generator 0.71.0. That is
not part of this change: #70670 raised the declared floor to >=0.71.0 without
regenerating uv.lock, leaving the lock pinned at a version its own constraint
excludes, so any `uv lock` has to correct it.

Report URL: https://github.com/apache/airflow/actions/runs/30605488364

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to