CI: update checkout, setup-python, setup-uv, codecov

[ChristianGeng]

Summary

Two related CI bugs, both caused by stale GitHub Action version pins:

1. Dead uv caching: astral-sh/setup-uv's default cache-dependency-glob
   keys on uv.lock/requirements*.txt, neither of which exists here (no
   committed lockfile, by design), so caching never actually worked. This
   repo's setup-uv pin was a SHA (3259c6206f993105e3a61b142c2d97bf4b9ef83d),
   which resolves to tag v7.1.0 — already past the fix that matters here
   (v6.0.0 added pyproject.toml to the default glob) and past the Node
   20 -> Node 24 runtime bump (v7.0.0). Bumping to v9.0.0 anyway, for
   consistency with the other repos in this cleanup.

2. Node.js 20 deprecation: actions/checkout and actions/setup-python
   bumped v4/v5 -> v7, clearing the "Node.js 20 is deprecated" warning.
   codecov/codecov-action bumped v4 -> v7; its v5 rewrite dropped the
   singular file: input in favor of files:, renamed accordingly. No
   actions/cache usage exists in this repo's workflows.

prune-cache left at its new default (off): audiofile's dependency tree
(audeer, audmath, numpy, soundfile) has no large pre-built binary wheels
like torch, so pruning would save ~0 disk space while costing avoidable
re-downloads.

Part of the same CI cleanup as audeering/audeer#206,
audeering/opensmile-python#132, audeering/audb#591,
audeering/audformat#539, audeering/audbackend#307, and
audeering/audresample#83.

Test plan

• All workflow YAML files reviewed and diff-verified against the
  established pattern from sibling repos
• CI passes on this PR

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates all GitHub Actions workflow pins to newer major versions to fix uv caching and eliminate Node.js 20 deprecation warnings, and adjusts Codecov inputs to the new API.

File-Level Changes

Change	Details	Files
Bump checkout and setup-python actions to v7 across all workflows to move off the Node.js 20 runtime.	Update actions/checkout from v4 to v7 in test, doc, linter, and publish workflows Update actions/setup-python from v5 to v7 in doc, linter, and publish workflows	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.yml
Update uv setup action to a tagged v9.0.0 to enable correct dependency caching on pyproject.toml and align with sibling repos.	Replace SHA-pinned astral-sh/setup-uv reference with tag v9.0.0 in all workflows using uv Rely on newer default cache-dependency-glob behavior that includes pyproject.toml, without adding custom cache config	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.yml
Modernize Codecov action usage to v7 and adapt configuration to the new inputs.	Bump codecov/codecov-action from v4 to v7 in test workflow Rename Codecov input from file to files to match the new action version while keeping the same coverage path	.github/workflows/test.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since this repo intentionally relies on pyproject.toml-based dependency resolution, consider explicitly setting cache-dependency-glob in astral-sh/setup-uv to include pyproject.toml rather than depending on the action’s default, so future default changes don’t silently break caching again.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since this repo intentionally relies on `pyproject.toml`-based dependency resolution, consider explicitly setting `cache-dependency-glob` in `astral-sh/setup-uv` to include `pyproject.toml` rather than depending on the action’s default, so future default changes don’t silently break caching again.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[ChristianGeng]

Re: making cache-dependency-glob explicit — relying on setup-uv's documented default (which includes pyproject.toml as of v6.0.0) is intentional here, for consistency across this whole rollout (audeer#206, opensmile-python#132, audb#591, audformat#539, audbackend#307, audresample#83, auglib#60, audinterface#206) — all of them lean on the same documented default rather than each repo carrying its own explicit glob. Fair point that a documented default can change again in the future, but that's true of any default we'd pin explicitly too. Leaving as-is.