alt Hacker NewsI would stick to older ruff until team has resources to fix issues and move to newer version. The same think you do with other dependencies.
I would stick to older ruff until team has resources to fix issues and move to newer version. The same think you do with other dependencies.
I find it hard to look at ruff as at "other dependencies."
First, my other dependencies usually deliver something of value to the customer (and so I deliver my other dependencies to the end-user installation.) Second, when I need to change code to accommodate other dependencies, it is usually limited to a couple of files, sometimes to a couple of modules; this change will touch much, much more than that. Third, my other dependencies at least play nice by implementing semver and bumping a major release on a breaking change.
Nothing of that applies to this change.
> fix issues
Which weren't "issues" at all just this morning.