[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.0.285 → v0.0.286

[codecov]

Codecov Report

Merging #1110 (49b90d2) into main (cb5b443) will decrease coverage by 2.09%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1110      +/-   ##
==========================================
- Coverage   84.79%   82.71%   -2.09%     
==========================================
  Files          36       36              
  Lines        5131     5131              
==========================================
- Hits         4351     4244     -107     
- Misses        780      887     +107     

Flag	Coverage Δ
gpu-tests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

see 6 files with indirect coverage changes

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 0.9.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 6c3c6d19a14cfccb5d37f0d32875675013ec9610

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #1110: [pre-commit.ci] pre-commit autoupdate'

4. Push to a named branch:

git push YOURFORK 0.9.x:auto-backport-of-pr-1110-on-0.9.x

5. Create a PR against branch 0.9.x, I would have named this PR:

"Backport PR #1110 on branch 0.9.x ([pre-commit.ci] pre-commit autoupdate)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.