I see manually updating libraries as a feature that allows for deterministic linting.
I wouldn't want my linter to always be updated to the latest version because that might introduce warnings or deprecation errors that aren't warnings or errors in the version of the tools used in the code I'm linting.
Most linters also don't require manual changes but do automatic fixing, ie: black[0].
Non-user initiated updates to QA tools will only lead to alert fatigue because people will write it off as an update to to tool.
Similarly they way Django Doctor works is more convenient:
- it's suggests a change that can be applied in one click - it's suggestion can be ignored - no overhead cost because it's SaaS
but yes, if you don't value SaaS in this context then that's fair enough :)
That said, if you live in Github and other SaaS services this fits really well. In the past I've setup similar workflow to cater to people who never dared to touch a terminal or Git itself. So there is certainly enablement this tool brings to some people.