chore: fix Python 3.8 compatibility issue

[huxuan]

---

📚 Documentation preview 📚: https://ss-python--368.org.readthedocs.build/en/368/

[huxuan]

@msclock This is the best solution I can come up with for the back compatibility hack.

It will install pre-commit 3.5.0 for Python 3.8 and will install the latest version for Python 3.9 and higher. Besides, the latest version is pinned and can be updated with renovate while the version 3.5.0 is pinned forever.

Any comments are welcome. :-)

[msclock]

@msclock This is the best solution I can come up with for the back compatibility hack.

It will install pre-commit 3.5.0 for Python 3.8 and will install the latest version for Python 3.9 and higher. Besides, the latest version is pinned and can be updated with renovate while the version 3.5.0 is pinned forever.

Any comments are welcome. :-)

Emm..., I consider the command without the pinned version pipx install pre-commit can dramatically reduce the implementation complexity.🤣

[huxuan]

Emm..., I consider the command without the pinned version pipx install pre-commit can dramatically reduce the implementation complexity.🤣

That is the state before renovate integration but may not be the best practice. Since we enabled the build cache, no pinned version will be treated as cache hit even when a new version released.

[msclock]

Emm..., I consider the command without the pinned version pipx install pre-commit can dramatically reduce the implementation complexity.🤣

That is the state before renovate integration but may not be the best practice. Since we enabled the build cache, no pinned version will be treated as cache hit even when a new version released.

I see the multiple phase build cache silences the update of pre-commit. The pr now is the solution.👌