washeck

Shall I prepare PR for the changelog entry? Now, when Django 5.1 alpha was released, the issue will become more visible.

@pajod I think this PR should be merged instead of mine https://github.com/benoitc/gunicorn/pull/3196 What are the next steps to merge it?

I think the issue we ran into is https://github.com/tiangolo/typer/issues/790 - typer probably issued somehow broken release. Based on you advice to use `safety` in isolated environment, I was thinking about...

I have a similar use case. My primary use of `ruff` in PyCharm is the formatter and while I have many linter options enabled in the config, I don't want...

This PR cannot be merged because `dependabot` created it with `poetry 1.3` which uses incompatible lock file format with `poetry-1.1.15` used in `pyzeebe` CI. I really like to see this...