[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.1.11 → v0.1.13

[codecov]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (30c5902) 72.70% compared to head (61c7efc) 72.37%.
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2811      +/-   ##
==========================================
- Coverage   72.70%   72.37%   -0.34%     
==========================================
  Files         111      111              
  Lines       12368    12368              
==========================================
- Hits         8992     8951      -41     
- Misses       3376     3417      +41     

Files	Coverage Δ
scanpy/experimental/pp/_highly_variable_genes.py	63.46% <100.00%> (ø)
scanpy/testing/_pytest/fixtures/data.py	100.00% <100.00%> (ø)
scanpy/preprocessing/_highly_variable_genes.py	96.17% <90.47%> (ø)

... and 1 file 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 1.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 4f4b1c3a655546d981360bcce625d354a4291385

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

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

4. Push to a named branch:

git push YOURFORK 1.9.x:auto-backport-of-pr-2811-on-1.9.x

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

"Backport PR #2811 on branch 1.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.