chore(deps): bump astral-sh/setup-uv from 5.4.2 to 7.1.6

[dependabot]

Bumps astral-sh/setup-uv from 5.4.2 to 7.1.6.

Release notes

Sourced from astral-sh/setup-uv's releases.

v7.1.6 🌈 add OS version to cache key to prevent binary incompatibility

Changes

This release will invalidate your cache existing keys!

The os version e.g. ubuntu-22.04 is now part of the cache key. This prevents failing builds when a cache got populated with wheels built with different tools (e.g. glibc) than are present on the runner where the cache got restored.

🐛 Bug fixes

• feat: add OS version to cache key to prevent binary incompatibility @​eifinger (#716)

🧰 Maintenance

• chore: update known checksums for 0.9.17 @github-actions[bot] (#714)

⬆️ Dependency updates

• Bump actions/checkout from 5.0.0 to 6.0.1 @dependabot[bot] (#712)
• Bump actions/setup-node from 6.0.0 to 6.1.0 @dependabot[bot] (#715)

v7.1.5 🌈 allow setting cache-local-path without enable-cache: true

Changes

astral-sh/setup-uv#612 fixed a faulty behavior where this action set UV_CACHE_DIR even though enable-cache was false. It also fixed the cases were the cache dir is already configured in a settings file like pyproject.toml or UV_CACHE_DIR was already set. Here the action shouldn't overwrite or set UV_CACHE_DIR.

These fixes introduced an unwanted behavior: You can still set cache-local-path but this action didn't do anything. This release fixes that.

You can now use cache-local-path to automatically set UV_CACHE_DIR even when enable-cache is false (or gets set to false by default e.g. on self-hosted runners)

- name: This is now possible
  uses: astral-sh/setup-uv@v7
  with:
    enable-cache: false
    cache-local-path: "/path/to/cache"

🐛 Bug fixes

• allow cache-local-path w/o enable-cache @​eifinger (#707)

🧰 Maintenance

• set biome files.maxSize to 2MiB @​eifinger (#708)
• chore: update known checksums for 0.9.16 @github-actions[bot] (#706)
• chore: update known checksums for 0.9.15 @github-actions[bot] (#704)
• chore: use npm ci --ignore-scripts everywhere @​woodruffw (#699)
• chore: update known checksums for 0.9.14 @github-actions[bot] (#700)
• chore: update known checksums for 0.9.13 @github-actions[bot] (#694)

... (truncated)

Commits

• 681c641 Bump actions/checkout from 5.0.0 to 6.0.1 (#712)
• 2e85713 Bump actions/setup-node from 6.0.0 to 6.1.0 (#715)
• 58b6d7b fix: add OS version to cache key to prevent binary incompatibility (#716)
• e8b52af chore: update known checksums for 0.9.17 (#714)
• ed21f2f Bump peter-evans/create-pull-request from 7.0.8 to 7.0.9 (#695)
• 93202d8 bump dependencies (#709)
• 5ce0900 set biome files.maxSize to 2MiB (#708)
• 4180991 allow cache-local-path w/o enable-cache (#707)
• 0439606 Bump github/codeql-action from 4.30.9 to 4.31.6 (#698)
• 7dd56c1 chore: update known checksums for 0.9.16 (#706)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jbdevprimary]

🔧 CI Fix Suggestion

Branch: dependabot/github_actions/astral-sh/setup-uv-7.1.6

1. Root Cause: The actions/download-artifact step failed because an artifact named build-output could not be found in the specified workflow run (20656555281) of the agentic-dev-library/control repository. This typically indicates the artifact was never uploaded, was uploaded with a different name, or the uploading job failed.

2. Suggested Fix: Verify the name used in the actions/upload-artifact step within the source workflow (in the agentic-dev-library/control repository) exactly matches build-output. Ensure the job that uploads the artifact is successfully completing and not being skipped by a conditional statement.

   # In the workflow that uploads the artifact
   - name: Upload artifact
     uses: actions/upload-artifact@v4
     with:
       # Ensure this name matches the download-artifact 'name' input
       name: build-output
       path: path/to/your/build/files

3. Commands to verify:

   1. Manually inspect the workflow run logs: Navigate to https://github.com/agentic-dev-library/control/actions/runs/20656555281.
   2. Check the run's "Artifacts" section to confirm if an artifact named build-output was created.
   3. If it doesn't exist, review the logs for the job tasked with uploading the artifact to diagnose why it failed or was skipped.

---

_{🤖 Generated by Ecosystem Fixer using Ollama GLM 4.6}

[dependabot]

Superseded by #71.