Update ruff, black and mypy versions.

[Ronimsenn]

The versions of the tools used are ~2 years behind current releases.
This leads to issues when you have the standalone versions of them installed for quick formatting during development for example.

Up-to-date versions (based on today):

• ruff-pre-commit: v0.9.7
• black: 25.1.0
• mirrors-mypy: v1.15.0

[dagshub]

Join the discussion on DagsHub!

[Ronimsenn]

Hey, happy to see you are back :)

I think it would be reasonable to do this via GitHub Actions and a weekly or daily schedule? Idk which scope is possible in a free plan of GitHub, but if you'd agree, I would have a look how to set it up maybe in my fork and create a pull when I figured it out?

[khuyentran1401]

Hi @Ronimsenn, do you mean to update the versions on a regular schedule? That sounds good to me. Let me know some ideas you have.

[khuyentran1401]

Also I conder adding uv to this project as well, what do you think? @Ronimsenn

[Ronimsenn]

Hi @Ronimsenn, do you mean to update the versions on a regular schedule? That sounds good to me. Let me know some ideas you have.

Exactly! My general idea would be a scheduled task (GitHub Action/Workflow), which runs every X day(s)/week(s) and compares the current versions of all hooks defined in the .pre-commit-config.yaml with the latest release of the corresponding GitHub repository.

It would be perfect, if it dynamically reads all hooks from the .pre-commit-config.yaml instead of having them hard-coded, but I'm not sure if it would break if you add a non-GitHub hook then.

Only issue: I didn't really have a look at the free GitHub plan's options for GitHub Actions/Workflows.

For now however, I would just create a short PR later to bump the versions up to date manually.

Also I conder adding uv to this project as well, what do you think? @Ronimsenn

Sounds good to me - I think uv is pretty awesome, and it would for sure extend the usability of this template IMO, as slowly more people will probably start using uv.

Maybe worth creating an own issue to keep these two topics separated?

[khuyentran1401]

Sounds great. I think the free GitHub plan's options for GitHub Actions/Workflows. It would be great if this can be automated so that you can focus on other tasks.

Yes, creating GitHub issues would be great. Thank you

[Ronimsenn]

Sounds great. I think the free GitHub plan's options for GitHub Actions/Workflows. It would be great if this can be automated so that you can focus on other tasks.

Agree! Will get started having a look at it soonish :)

Yes, creating GitHub issues would be great. Thank you

Done #28

[Ronimsenn]

Did the manual bump in #29 . I'll probably use a dedicated branch in my Fork starting prior to this bump for testing the workflow.
Hope I'll be able to get started with it tomorrow.

[khuyentran1401]

Sounds great! Thanks a lot @Ronimsenn

[Ronimsenn]

I've been researching a bit, as there already have been some attempts to write this (obviously).
By clicking through the a bit outdated, you you wanna use this...-Links, I ended up here: https://pre-commit.ci/

To me, it seems to be a GitHub hosted (! not developed by GitHub) CI Tool especially for precommit updates.
I would give it a try in my Fork and see if it works well.

The updates are scheduled Mondays around 16:00 UTC, so it will take a few days before I can share results.

[khuyentran1401]

Sounds great! Thanks for digging into this and thanks for the update

[khuyentran1401]

@Ronimsenn FYI, I have just removed black and use ruff formatter instead as it is a drop-in replacement for black #31

[Ronimsenn]

Okay, thx for the heads up!