Should python `ruff` fixer default to pass `--no-fix` on newer versions?

I recently had a lot of trouble figuring out how to configure `ruff` for use with ALE.
I found that the `ruff` linter was consistently failing with somewhat inscrutable messages.

It turned out that the default invocation pattern being used produces a fully fixed file as output under the latest `ruff` versions.

Adding `--no-fix` to the linter config fixed it, but I suspect that other users are struggling with this.
I might try to put together a PR for this at some point, but can't commit to that at present.