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

[ChristianGeng]

Summary

• setup-uv's cache keys on uv.lock/requirements*.txt, neither of which exists here (no committed lockfile, by design), so caching never actually worked. Bumped astral-sh/setup-uv v4/v5 -> v9.0.0 (publish.yml had both, in its two jobs): v9.0.0's default glob adds pyproject.toml, which is committed and changes exactly when a dependency does — so caching now works with no lockfile needed.
• Also bumped actions/checkout and actions/setup-python to v7 across all four workflows, and codecov/codecov-action to v7 in test.yml, clearing the "Node.js 20 is deprecated" warning entirely. codecov-action's v5 rewrite dropped the file input this workflow used; renamed to files, its replacement.
• Left prune-cache at its new default (off): opensmile-python's only runtime dependencies are audobject and audinterface, with no torch-scale binary wheels in the dependency tree, so per astral-sh/setup-uv#967 pruning wouldn't pay off here either.

Test plan

• git diff limited to the exact action-version bumps (+ the one file -> files rename), no other content touched
• All 4 changed workflow YAML files parse via yaml.safe_load
• CI run on this PR shows green + a working uv cache hit on subsequent runs

---

Same fix already merged as audeering/audeer#206, ported here for consistency.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates all GitHub Actions workflows to use newer major versions of checkout, setup-python, setup-uv, and codecov, and adjusts uv caching and Codecov inputs to align with the new action defaults and APIs so caching works without a lockfile and Node.js 20 deprecation warnings are removed.

Flow diagram for updated CI dependency caching with setup-uv

flowchart TD
    A[GitHub_Actions_workflow] --> B[actions_checkout_v7]
    B --> C[actions_setup_python_v7]
    C --> D[setup_uv_v9_0_0]
    D --> E[uv_cache_key_includes_pyproject_toml]
    E --> F[uv_sync_installs_dependencies]
    F --> G[tests_and_linting_run]

Loading

File-Level Changes

Change	Details	Files
Update GitHub Actions workflows to use latest major versions of checkout and setup-python to address Node.js 20 deprecation.	Bump actions/checkout from v4 to v7 in all workflows Bump actions/setup-python from v5 to v7 in all workflows	.github/workflows/publish.yml .github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml
Align uv setup and caching behavior with current astral-sh/setup-uv defaults so caching works with pyproject.toml instead of a lockfile.	Bump astral-sh/setup-uv from v4/v5 to v9.0.0 across all workflows Rely on v9.0.0 default cache key glob that includes pyproject.toml so caching functions without uv.lock or requirements files Keep prune-cache at its default disabled state, given the project’s lightweight dependency tree	.github/workflows/publish.yml .github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml
Update Codecov action usage to the latest major version and its revised inputs API.	Bump codecov/codecov-action from v4 to v7 in the test workflow Rename input key from file to files to match the v5+ Codecov action API	.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 found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path=".github/workflows/publish.yml" line_range="27-33" />
<code_context>

     steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@v7

     - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v5
+      uses: actions/setup-python@v7
       with:
         python-version: ${{ matrix.python-version }}
</code_context>
<issue_to_address>
**issue (bug_risk):** actions/checkout/setup-python v7 tags may not exist and could break the workflow

These versions are ahead of the currently released majors (checkout v4, setup-python v5). If v7 tags don’t exist in your GitHub environment, the workflow will fail when resolving the actions. Please pin to existing major versions or verified tags instead.
</issue_to_address>

---

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.}

[hagenw]

I guess the documentation build is failing as the audb repos are not up-to-date.

[ChristianGeng]

Confirmed — pre-existing and unrelated to this PR. The failure is RuntimeError: Cannot find version '1.1.1' for database 'emodb' when building usage.rst; it's not that audb itself is stale, it's that emodb v1.1.1 (hardcoded in the docs) has apparently been pruned from the audb-hosted repo. Same failure on main predates this PR — last green Documentation run was 2025-10-27. Out of scope here; happy to open a separate issue to bump the pinned emodb version in the docs if useful.

[hagenw]

Yes, open a separate issue. But feel free to merge here already without succeeding pipeline.