mirror of
https://github.com/adrienverge/yamllint.git
synced 2026-10-30 09:30:27 -05:00
gauravandClaude Opus 5
f4ad063adb
ruff 0.16.0 (released 2026-07-23) stabilized `ISC004` `implicit-string-concatenation-in-collection-literal` out of preview. https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md#stabilization https://docs.astral.sh/ruff/rules/implicit-string-concatenation-in-collection-literal Since `ruff` is unpinned in `dependency-groups.dev` and `pyproject.toml` selects the whole `ISC` family, the `Linters` job now fails on `master` and on every open PR with 7 errors in `tests/test_cli.py` and `tests/test_config.py`. Master's last green run was 2026-07-20, three days before the release. This applies the rule to the 7 affected sites by parenthesizing the concatenations. Where the extra indentation would have pushed a line past the 79-column limit, the enclosing `assertEqual(...)` call is wrapped instead of re-splitting the strings, so **every string literal is byte-identical to `master`** — verified by comparing all `ast.Constant` string nodes before and after (435/435 in `test_cli.py`, 539/539 in `test_config.py`). Verified locally with ruff 0.16.0: `ruff check`, `flake8`, `doc8`, `rstcheck`, `yamllint --strict` and `make -C docs html` all clean, and `python -X warn_default_encoding -W error::EncodingWarning -m unittest discover` passes 432 tests. Separately, you may want to consider upper-bounding `ruff` in `dependency-groups.dev` so that a ruff release can't turn unrelated PRs red — but that's a policy call, and the `style: Apply ruff rule X` history suggests you may prefer riding latest. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>