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. Bumped
   astral-sh/setup-uvv5 -> v9.0.0: v6.0.0 added pyproject.toml to
   the default glob, which is committed and changes exactly when a
   dependency does, so caching now works with no lockfile needed.

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.
   actions/cache (used for the emodb test-data cache in doc/test
   workflows) bumped v4 -> v6 for the same reason.

prune-cache left at its new default (off): audinterface's dependency tree
(audeer, audformat, audiofile, audmath, audresample) 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 GitHub Actions workflows to modern action versions, fixing uv dependency caching and removing Node.js 20 deprecation warnings, plus adjusting Codecov config for the newer action API.

Flow diagram for updated CI workflows using new GitHub Actions versions

flowchart TD
GH[GitHub Actions workflow] --> DOC[doc.yml job]
GH --> LINT[linter.yml job]
GH --> PUBLISH[publish.yml job]
subgraph DocJob
DOC --> CkDoc[actions_checkout_v7]
CkDoc --> CacheDoc[actions_cache_v6 emodb]
CacheDoc --> PyDoc[actions_setup_python_v7]
PyDoc --> UvDoc[astral_sh_setup_uv_v9_0_0]
end
subgraph LinterJob
LINT --> CkLint[actions_checkout_v7]
CkLint --> PyLint[actions_setup_python_v7]
PyLint --> UvLint[astral_sh_setup_uv_v9_0_0]
end
subgraph PublishJob
PUBLISH --> CkPub[actions_checkout_v7]
CkPub --> PyPub[actions_setup_python_v7]
PyPub --> UvPub[astral_sh_setup_uv_v9_0_0]
end
UvDoc --> UvCache[uv cache keyed by pyproject.toml]

Loading

File-Level Changes

Change	Details	Files
Modernize CI workflows by bumping core GitHub Actions and fixing uv caching and Codecov configuration.	Bump actions/checkout from v4 to v7 across all workflows to move off the Node.js 20 runtime. Bump actions/setup-python from v5 to v7 in all workflows to align with the latest runtime and feature set. Bump actions/cache from v4 to v6 in test and doc workflows for the emodb cache to match the supported runtime. Bump astral-sh/setup-uv from v5 to v9.0.0 in all workflows so the default cache-dependency-glob includes pyproject.toml and uv caching becomes effective without a lockfile. Bump codecov/codecov-action from v4 to v7 in the test workflow and update the input from file: to files: ./coverage.xml to satisfy the new action interface.	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.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:

• Consider pinning astral-sh/setup-uv to the major version (e.g., @v9) rather than a specific patch (@v9.0.0) to automatically pick up compatible patch updates without needing manual bumps.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments- Consider pinning `astral-sh/setup-uv` to the major version (e.g., `@v9`) rather than a specific patch (`@v9.0.0`) to automatically pick up compatible patch updates without needing manual bumps.

---

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: the version-pin suggestion — pinning astral-sh/setup-uv to the exact v9.0.0 tag rather than floating v9 is intentional here, not an oversight. This bump exists specifically to land the caching fix that landed in v6.0.0 (adding pyproject.toml to the default cache-dependency-glob), so pinning the exact version we verified against avoids silently picking up a future patch release we haven't tested. Same choice made across the sibling repos in this rollout (audeer#206, opensmile-python#132, audb#591, audformat#539, audbackend#307, audresample#83, auglib#60) — checkout/setup-python/codecov-action float on major tags by convention, setup-uv is pinned exact because this PR's whole point is a specific version's behavior change. Leaving as-is.

[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. Bumped
   astral-sh/setup-uvv5 -> v9.0.0: v6.0.0 added pyproject.toml to
   the default glob, which is committed and changes exactly when a
   dependency does, so caching now works with no lockfile needed.

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.
   actions/cache (used for the emodb test-data cache in doc/test
   workflows) bumped v4 -> v6 for the same reason.

prune-cache left at its new default (off): audinterface's dependency tree
(audeer, audformat, audiofile, audmath, audresample) 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 GitHub Actions workflows to modern action versions, fixing uv dependency caching and removing Node.js 20 deprecation warnings, plus adjusting Codecov config for the newer action API.

Flow diagram for updated CI workflows using new GitHub Actions versions

flowchart TD
GH[GitHub Actions workflow] --> DOC[doc.yml job]
GH --> LINT[linter.yml job]
GH --> PUBLISH[publish.yml job]
subgraph DocJob
DOC --> CkDoc[actions_checkout_v7]
CkDoc --> CacheDoc[actions_cache_v6 emodb]
CacheDoc --> PyDoc[actions_setup_python_v7]
PyDoc --> UvDoc[astral_sh_setup_uv_v9_0_0]
end
subgraph LinterJob
LINT --> CkLint[actions_checkout_v7]
CkLint --> PyLint[actions_setup_python_v7]
PyLint --> UvLint[astral_sh_setup_uv_v9_0_0]
end
subgraph PublishJob
PUBLISH --> CkPub[actions_checkout_v7]
CkPub --> PyPub[actions_setup_python_v7]
PyPub --> UvPub[astral_sh_setup_uv_v9_0_0]
end
UvDoc --> UvCache[uv cache keyed by pyproject.toml]

Loading

File-Level Changes

Change	Details	Files
Modernize CI workflows by bumping core GitHub Actions and fixing uv caching and Codecov configuration.	Bump actions/checkout from v4 to v7 across all workflows to move off the Node.js 20 runtime. Bump actions/setup-python from v5 to v7 in all workflows to align with the latest runtime and feature set. Bump actions/cache from v4 to v6 in test and doc workflows for the emodb cache to match the supported runtime. Bump astral-sh/setup-uv from v5 to v9.0.0 in all workflows so the default cache-dependency-glob includes pyproject.toml and uv caching becomes effective without a lockfile. Bump codecov/codecov-action from v4 to v7 in the test workflow and update the input from file: to files: ./coverage.xml to satisfy the new action interface.	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.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:

• Consider pinning astral-sh/setup-uv to the major version (e.g., @v9) rather than a specific patch (@v9.0.0) to automatically pick up compatible patch updates without needing manual bumps.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments- Consider pinning `astral-sh/setup-uv` to the major version (e.g., `@v9`) rather than a specific patch (`@v9.0.0`) to automatically pick up compatible patch updates without needing manual bumps.

---

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: the version-pin suggestion — pinning astral-sh/setup-uv to the exact v9.0.0 tag rather than floating v9 is intentional here, not an oversight. This bump exists specifically to land the caching fix that landed in v6.0.0 (adding pyproject.toml to the default cache-dependency-glob), so pinning the exact version we verified against avoids silently picking up a future patch release we haven't tested. Same choice made across the sibling repos in this rollout (audeer#206, opensmile-python#132, audb#591, audformat#539, audbackend#307, audresample#83, auglib#60) — checkout/setup-python/codecov-action float on major tags by convention, setup-uv is pinned exact because this PR's whole point is a specific version's behavior change. Leaving as-is.

[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. Bumped
   astral-sh/setup-uvv5 -> v9.0.0: v6.0.0 added pyproject.toml to
   the default glob, which is committed and changes exactly when a
   dependency does, so caching now works with no lockfile needed.

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.
   actions/cache (used for the emodb test-data cache in doc/test
   workflows) bumped v4 -> v6 for the same reason.

prune-cache left at its new default (off): audinterface's dependency tree
(audeer, audformat, audiofile, audmath, audresample) 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 GitHub Actions workflows to modern action versions, fixing uv dependency caching and removing Node.js 20 deprecation warnings, plus adjusting Codecov config for the newer action API.

Flow diagram for updated CI workflows using new GitHub Actions versions

flowchart TD
GH[GitHub Actions workflow] --> DOC[doc.yml job]
GH --> LINT[linter.yml job]
GH --> PUBLISH[publish.yml job]
subgraph DocJob
DOC --> CkDoc[actions_checkout_v7]
CkDoc --> CacheDoc[actions_cache_v6 emodb]
CacheDoc --> PyDoc[actions_setup_python_v7]
PyDoc --> UvDoc[astral_sh_setup_uv_v9_0_0]
end
subgraph LinterJob
LINT --> CkLint[actions_checkout_v7]
CkLint --> PyLint[actions_setup_python_v7]
PyLint --> UvLint[astral_sh_setup_uv_v9_0_0]
end
subgraph PublishJob
PUBLISH --> CkPub[actions_checkout_v7]
CkPub --> PyPub[actions_setup_python_v7]
PyPub --> UvPub[astral_sh_setup_uv_v9_0_0]
end
UvDoc --> UvCache[uv cache keyed by pyproject.toml]

Loading

File-Level Changes

Change	Details	Files
Modernize CI workflows by bumping core GitHub Actions and fixing uv caching and Codecov configuration.	Bump actions/checkout from v4 to v7 across all workflows to move off the Node.js 20 runtime. Bump actions/setup-python from v5 to v7 in all workflows to align with the latest runtime and feature set. Bump actions/cache from v4 to v6 in test and doc workflows for the emodb cache to match the supported runtime. Bump astral-sh/setup-uv from v5 to v9.0.0 in all workflows so the default cache-dependency-glob includes pyproject.toml and uv caching becomes effective without a lockfile. Bump codecov/codecov-action from v4 to v7 in the test workflow and update the input from file: to files: ./coverage.xml to satisfy the new action interface.	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.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:

• Consider pinning astral-sh/setup-uv to the major version (e.g., @v9) rather than a specific patch (@v9.0.0) to automatically pick up compatible patch updates without needing manual bumps.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments- Consider pinning `astral-sh/setup-uv` to the major version (e.g., `@v9`) rather than a specific patch (`@v9.0.0`) to automatically pick up compatible patch updates without needing manual bumps.

---

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: the version-pin suggestion — pinning astral-sh/setup-uv to the exact v9.0.0 tag rather than floating v9 is intentional here, not an oversight. This bump exists specifically to land the caching fix that landed in v6.0.0 (adding pyproject.toml to the default cache-dependency-glob), so pinning the exact version we verified against avoids silently picking up a future patch release we haven't tested. Same choice made across the sibling repos in this rollout (audeer#206, opensmile-python#132, audb#591, audformat#539, audbackend#307, audresample#83, auglib#60) — checkout/setup-python/codecov-action float on major tags by convention, setup-uv is pinned exact because this PR's whole point is a specific version's behavior change. Leaving as-is.

[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. Bumped
   astral-sh/setup-uvv5 -> v9.0.0: v6.0.0 added pyproject.toml to
   the default glob, which is committed and changes exactly when a
   dependency does, so caching now works with no lockfile needed.

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.
   actions/cache (used for the emodb test-data cache in doc/test
   workflows) bumped v4 -> v6 for the same reason.

prune-cache left at its new default (off): audinterface's dependency tree
(audeer, audformat, audiofile, audmath, audresample) 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 GitHub Actions workflows to modern action versions, fixing uv dependency caching and removing Node.js 20 deprecation warnings, plus adjusting Codecov config for the newer action API.

Flow diagram for updated CI workflows using new GitHub Actions versions

flowchart TD
GH[GitHub Actions workflow] --> DOC[doc.yml job]
GH --> LINT[linter.yml job]
GH --> PUBLISH[publish.yml job]
subgraph DocJob
DOC --> CkDoc[actions_checkout_v7]
CkDoc --> CacheDoc[actions_cache_v6 emodb]
CacheDoc --> PyDoc[actions_setup_python_v7]
PyDoc --> UvDoc[astral_sh_setup_uv_v9_0_0]
end
subgraph LinterJob
LINT --> CkLint[actions_checkout_v7]
CkLint --> PyLint[actions_setup_python_v7]
PyLint --> UvLint[astral_sh_setup_uv_v9_0_0]
end
subgraph PublishJob
PUBLISH --> CkPub[actions_checkout_v7]
CkPub --> PyPub[actions_setup_python_v7]
PyPub --> UvPub[astral_sh_setup_uv_v9_0_0]
end
UvDoc --> UvCache[uv cache keyed by pyproject.toml]

Loading

File-Level Changes

Change	Details	Files
Modernize CI workflows by bumping core GitHub Actions and fixing uv caching and Codecov configuration.	Bump actions/checkout from v4 to v7 across all workflows to move off the Node.js 20 runtime. Bump actions/setup-python from v5 to v7 in all workflows to align with the latest runtime and feature set. Bump actions/cache from v4 to v6 in test and doc workflows for the emodb cache to match the supported runtime. Bump astral-sh/setup-uv from v5 to v9.0.0 in all workflows so the default cache-dependency-glob includes pyproject.toml and uv caching becomes effective without a lockfile. Bump codecov/codecov-action from v4 to v7 in the test workflow and update the input from file: to files: ./coverage.xml to satisfy the new action interface.	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.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:

• Consider pinning astral-sh/setup-uv to the major version (e.g., @v9) rather than a specific patch (@v9.0.0) to automatically pick up compatible patch updates without needing manual bumps.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments- Consider pinning `astral-sh/setup-uv` to the major version (e.g., `@v9`) rather than a specific patch (`@v9.0.0`) to automatically pick up compatible patch updates without needing manual bumps.

---

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: the version-pin suggestion — pinning astral-sh/setup-uv to the exact v9.0.0 tag rather than floating v9 is intentional here, not an oversight. This bump exists specifically to land the caching fix that landed in v6.0.0 (adding pyproject.toml to the default cache-dependency-glob), so pinning the exact version we verified against avoids silently picking up a future patch release we haven't tested. Same choice made across the sibling repos in this rollout (audeer#206, opensmile-python#132, audb#591, audformat#539, audbackend#307, audresample#83, auglib#60) — checkout/setup-python/codecov-action float on major tags by convention, setup-uv is pinned exact because this PR's whole point is a specific version's behavior change. Leaving as-is.

[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. Bumped
   astral-sh/setup-uvv5 -> v9.0.0: v6.0.0 added pyproject.toml to
   the default glob, which is committed and changes exactly when a
   dependency does, so caching now works with no lockfile needed.

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.
   actions/cache (used for the emodb test-data cache in doc/test
   workflows) bumped v4 -> v6 for the same reason.

prune-cache left at its new default (off): audinterface's dependency tree
(audeer, audformat, audiofile, audmath, audresample) 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 GitHub Actions workflows to modern action versions, fixing uv dependency caching and removing Node.js 20 deprecation warnings, plus adjusting Codecov config for the newer action API.

Flow diagram for updated CI workflows using new GitHub Actions versions

flowchart TD
GH[GitHub Actions workflow] --> DOC[doc.yml job]
GH --> LINT[linter.yml job]
GH --> PUBLISH[publish.yml job]
subgraph DocJob
DOC --> CkDoc[actions_checkout_v7]
CkDoc --> CacheDoc[actions_cache_v6 emodb]
CacheDoc --> PyDoc[actions_setup_python_v7]
PyDoc --> UvDoc[astral_sh_setup_uv_v9_0_0]
end
subgraph LinterJob
LINT --> CkLint[actions_checkout_v7]
CkLint --> PyLint[actions_setup_python_v7]
PyLint --> UvLint[astral_sh_setup_uv_v9_0_0]
end
subgraph PublishJob
PUBLISH --> CkPub[actions_checkout_v7]
CkPub --> PyPub[actions_setup_python_v7]
PyPub --> UvPub[astral_sh_setup_uv_v9_0_0]
end
UvDoc --> UvCache[uv cache keyed by pyproject.toml]

Loading

File-Level Changes

Change	Details	Files
Modernize CI workflows by bumping core GitHub Actions and fixing uv caching and Codecov configuration.	Bump actions/checkout from v4 to v7 across all workflows to move off the Node.js 20 runtime. Bump actions/setup-python from v5 to v7 in all workflows to align with the latest runtime and feature set. Bump actions/cache from v4 to v6 in test and doc workflows for the emodb cache to match the supported runtime. Bump astral-sh/setup-uv from v5 to v9.0.0 in all workflows so the default cache-dependency-glob includes pyproject.toml and uv caching becomes effective without a lockfile. Bump codecov/codecov-action from v4 to v7 in the test workflow and update the input from file: to files: ./coverage.xml to satisfy the new action interface.	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.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:

• Consider pinning astral-sh/setup-uv to the major version (e.g., @v9) rather than a specific patch (@v9.0.0) to automatically pick up compatible patch updates without needing manual bumps.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments- Consider pinning `astral-sh/setup-uv` to the major version (e.g., `@v9`) rather than a specific patch (`@v9.0.0`) to automatically pick up compatible patch updates without needing manual bumps.

---

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: the version-pin suggestion — pinning astral-sh/setup-uv to the exact v9.0.0 tag rather than floating v9 is intentional here, not an oversight. This bump exists specifically to land the caching fix that landed in v6.0.0 (adding pyproject.toml to the default cache-dependency-glob), so pinning the exact version we verified against avoids silently picking up a future patch release we haven't tested. Same choice made across the sibling repos in this rollout (audeer#206, opensmile-python#132, audb#591, audformat#539, audbackend#307, audresample#83, auglib#60) — checkout/setup-python/codecov-action float on major tags by convention, setup-uv is pinned exact because this PR's whole point is a specific version's behavior change. Leaving as-is.

[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. Bumped
   astral-sh/setup-uvv5 -> v9.0.0: v6.0.0 added pyproject.toml to
   the default glob, which is committed and changes exactly when a
   dependency does, so caching now works with no lockfile needed.

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.
   actions/cache (used for the emodb test-data cache in doc/test
   workflows) bumped v4 -> v6 for the same reason.

prune-cache left at its new default (off): audinterface's dependency tree
(audeer, audformat, audiofile, audmath, audresample) 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 GitHub Actions workflows to modern action versions, fixing uv dependency caching and removing Node.js 20 deprecation warnings, plus adjusting Codecov config for the newer action API.

Flow diagram for updated CI workflows using new GitHub Actions versions

flowchart TD
GH[GitHub Actions workflow] --> DOC[doc.yml job]
GH --> LINT[linter.yml job]
GH --> PUBLISH[publish.yml job]
subgraph DocJob
DOC --> CkDoc[actions_checkout_v7]
CkDoc --> CacheDoc[actions_cache_v6 emodb]
CacheDoc --> PyDoc[actions_setup_python_v7]
PyDoc --> UvDoc[astral_sh_setup_uv_v9_0_0]
end
subgraph LinterJob
LINT --> CkLint[actions_checkout_v7]
CkLint --> PyLint[actions_setup_python_v7]
PyLint --> UvLint[astral_sh_setup_uv_v9_0_0]
end
subgraph PublishJob
PUBLISH --> CkPub[actions_checkout_v7]
CkPub --> PyPub[actions_setup_python_v7]
PyPub --> UvPub[astral_sh_setup_uv_v9_0_0]
end
UvDoc --> UvCache[uv cache keyed by pyproject.toml]

Loading

File-Level Changes

Change	Details	Files
Modernize CI workflows by bumping core GitHub Actions and fixing uv caching and Codecov configuration.	Bump actions/checkout from v4 to v7 across all workflows to move off the Node.js 20 runtime. Bump actions/setup-python from v5 to v7 in all workflows to align with the latest runtime and feature set. Bump actions/cache from v4 to v6 in test and doc workflows for the emodb cache to match the supported runtime. Bump astral-sh/setup-uv from v5 to v9.0.0 in all workflows so the default cache-dependency-glob includes pyproject.toml and uv caching becomes effective without a lockfile. Bump codecov/codecov-action from v4 to v7 in the test workflow and update the input from file: to files: ./coverage.xml to satisfy the new action interface.	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.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:

• Consider pinning astral-sh/setup-uv to the major version (e.g., @v9) rather than a specific patch (@v9.0.0) to automatically pick up compatible patch updates without needing manual bumps.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments- Consider pinning `astral-sh/setup-uv` to the major version (e.g., `@v9`) rather than a specific patch (`@v9.0.0`) to automatically pick up compatible patch updates without needing manual bumps.

---

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: the version-pin suggestion — pinning astral-sh/setup-uv to the exact v9.0.0 tag rather than floating v9 is intentional here, not an oversight. This bump exists specifically to land the caching fix that landed in v6.0.0 (adding pyproject.toml to the default cache-dependency-glob), so pinning the exact version we verified against avoids silently picking up a future patch release we haven't tested. Same choice made across the sibling repos in this rollout (audeer#206, opensmile-python#132, audb#591, audformat#539, audbackend#307, audresample#83, auglib#60) — checkout/setup-python/codecov-action float on major tags by convention, setup-uv is pinned exact because this PR's whole point is a specific version's behavior change. Leaving as-is.

[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. Bumped
   astral-sh/setup-uvv5 -> v9.0.0: v6.0.0 added pyproject.toml to
   the default glob, which is committed and changes exactly when a
   dependency does, so caching now works with no lockfile needed.

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.
   actions/cache (used for the emodb test-data cache in doc/test
   workflows) bumped v4 -> v6 for the same reason.

prune-cache left at its new default (off): audinterface's dependency tree
(audeer, audformat, audiofile, audmath, audresample) 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 GitHub Actions workflows to modern action versions, fixing uv dependency caching and removing Node.js 20 deprecation warnings, plus adjusting Codecov config for the newer action API.

Flow diagram for updated CI workflows using new GitHub Actions versions

flowchart TD
GH[GitHub Actions workflow] --> DOC[doc.yml job]
GH --> LINT[linter.yml job]
GH --> PUBLISH[publish.yml job]
subgraph DocJob
DOC --> CkDoc[actions_checkout_v7]
CkDoc --> CacheDoc[actions_cache_v6 emodb]
CacheDoc --> PyDoc[actions_setup_python_v7]
PyDoc --> UvDoc[astral_sh_setup_uv_v9_0_0]
end
subgraph LinterJob
LINT --> CkLint[actions_checkout_v7]
CkLint --> PyLint[actions_setup_python_v7]
PyLint --> UvLint[astral_sh_setup_uv_v9_0_0]
end
subgraph PublishJob
PUBLISH --> CkPub[actions_checkout_v7]
CkPub --> PyPub[actions_setup_python_v7]
PyPub --> UvPub[astral_sh_setup_uv_v9_0_0]
end
UvDoc --> UvCache[uv cache keyed by pyproject.toml]

Loading

File-Level Changes

Change	Details	Files
Modernize CI workflows by bumping core GitHub Actions and fixing uv caching and Codecov configuration.	Bump actions/checkout from v4 to v7 across all workflows to move off the Node.js 20 runtime. Bump actions/setup-python from v5 to v7 in all workflows to align with the latest runtime and feature set. Bump actions/cache from v4 to v6 in test and doc workflows for the emodb cache to match the supported runtime. Bump astral-sh/setup-uv from v5 to v9.0.0 in all workflows so the default cache-dependency-glob includes pyproject.toml and uv caching becomes effective without a lockfile. Bump codecov/codecov-action from v4 to v7 in the test workflow and update the input from file: to files: ./coverage.xml to satisfy the new action interface.	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.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:

• Consider pinning astral-sh/setup-uv to the major version (e.g., @v9) rather than a specific patch (@v9.0.0) to automatically pick up compatible patch updates without needing manual bumps.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments- Consider pinning `astral-sh/setup-uv` to the major version (e.g., `@v9`) rather than a specific patch (`@v9.0.0`) to automatically pick up compatible patch updates without needing manual bumps.

---

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: the version-pin suggestion — pinning astral-sh/setup-uv to the exact v9.0.0 tag rather than floating v9 is intentional here, not an oversight. This bump exists specifically to land the caching fix that landed in v6.0.0 (adding pyproject.toml to the default cache-dependency-glob), so pinning the exact version we verified against avoids silently picking up a future patch release we haven't tested. Same choice made across the sibling repos in this rollout (audeer#206, opensmile-python#132, audb#591, audformat#539, audbackend#307, audresample#83, auglib#60) — checkout/setup-python/codecov-action float on major tags by convention, setup-uv is pinned exact because this PR's whole point is a specific version's behavior change. Leaving as-is.

[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. Bumped
   astral-sh/setup-uvv5 -> v9.0.0: v6.0.0 added pyproject.toml to
   the default glob, which is committed and changes exactly when a
   dependency does, so caching now works with no lockfile needed.

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.
   actions/cache (used for the emodb test-data cache in doc/test
   workflows) bumped v4 -> v6 for the same reason.

prune-cache left at its new default (off): audinterface's dependency tree
(audeer, audformat, audiofile, audmath, audresample) 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 GitHub Actions workflows to modern action versions, fixing uv dependency caching and removing Node.js 20 deprecation warnings, plus adjusting Codecov config for the newer action API.

Flow diagram for updated CI workflows using new GitHub Actions versions

flowchart TD
GH[GitHub Actions workflow] --> DOC[doc.yml job]
GH --> LINT[linter.yml job]
GH --> PUBLISH[publish.yml job]
subgraph DocJob
DOC --> CkDoc[actions_checkout_v7]
CkDoc --> CacheDoc[actions_cache_v6 emodb]
CacheDoc --> PyDoc[actions_setup_python_v7]
PyDoc --> UvDoc[astral_sh_setup_uv_v9_0_0]
end
subgraph LinterJob
LINT --> CkLint[actions_checkout_v7]
CkLint --> PyLint[actions_setup_python_v7]
PyLint --> UvLint[astral_sh_setup_uv_v9_0_0]
end
subgraph PublishJob
PUBLISH --> CkPub[actions_checkout_v7]
CkPub --> PyPub[actions_setup_python_v7]
PyPub --> UvPub[astral_sh_setup_uv_v9_0_0]
end
UvDoc --> UvCache[uv cache keyed by pyproject.toml]

Loading

File-Level Changes

Change	Details	Files
Modernize CI workflows by bumping core GitHub Actions and fixing uv caching and Codecov configuration.	Bump actions/checkout from v4 to v7 across all workflows to move off the Node.js 20 runtime. Bump actions/setup-python from v5 to v7 in all workflows to align with the latest runtime and feature set. Bump actions/cache from v4 to v6 in test and doc workflows for the emodb cache to match the supported runtime. Bump astral-sh/setup-uv from v5 to v9.0.0 in all workflows so the default cache-dependency-glob includes pyproject.toml and uv caching becomes effective without a lockfile. Bump codecov/codecov-action from v4 to v7 in the test workflow and update the input from file: to files: ./coverage.xml to satisfy the new action interface.	.github/workflows/test.yml .github/workflows/doc.yml .github/workflows/linter.yml .github/workflows/publish.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:

• Consider pinning astral-sh/setup-uv to the major version (e.g., @v9) rather than a specific patch (@v9.0.0) to automatically pick up compatible patch updates without needing manual bumps.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments- Consider pinning `astral-sh/setup-uv` to the major version (e.g., `@v9`) rather than a specific patch (`@v9.0.0`) to automatically pick up compatible patch updates without needing manual bumps.

---

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: the version-pin suggestion — pinning astral-sh/setup-uv to the exact v9.0.0 tag rather than floating v9 is intentional here, not an oversight. This bump exists specifically to land the caching fix that landed in v6.0.0 (adding pyproject.toml to the default cache-dependency-glob), so pinning the exact version we verified against avoids silently picking up a future patch release we haven't tested. Same choice made across the sibling repos in this rollout (audeer#206, opensmile-python#132, audb#591, audformat#539, audbackend#307, audresample#83, auglib#60) — checkout/setup-python/codecov-action float on major tags by convention, setup-uv is pinned exact because this PR's whole point is a specific version's behavior change. Leaving as-is.