Feature request: Default to Ruff version from project setup

[cknowles]

At the moment the action defaults to the latest version of Ruff. In order to match local behaviour, it would be good if the action defaulted to the version matching that inside pyproject.toml / poetry.lock.

[Avasam]

There's some issues and hidden complexity with that:

• Support for different tools
  • you just mentioned poetry as an example
  • there's uv dev dependencies too for another
  • Good ol' requirements files
• Finding it in extras (like .[test] or .[dev])
• Mixed version ranges
• What to do about system and platforms restrictions ?

It'd be nice, but I don't think you should hold your breath on this, and instead just find the version string yourself with an easy string search srcipt. Here's an example with powershell: https://github.com/Avasam/typed-D3DShot/blob/24954b8122448926b9afddc1c245796b5e9165a0/.github/workflows/checks.yml#L24-L34 Here's one with Bash: https://github.com/Toufool/AutoSplit/blob/bd6cf54fdd3569c769e5c9d4ef9aab64344fca84/.github/workflows/lint-and-build.yml#L81-L94

Note that you'll have to extract an exact version (see #11)

[pjonsson]

My guess is that some mechanism that attempts to pick the Ruff version from the project setup, and fail with an error message if the version can't be determined automatically would satisfy most people. The few projects that have complex setups that use different versions of Ruff for different platform/systems can then set the version in the action instead.

Here's how the black action does it: https://github.com/psf/black/pull/4294. It would be nice if the Ruff action just works without having to add some other action to get Python 3.11 configured first.