Bump astral-sh/setup-uv from 5 to 7

[dependabot]

Bumps astral-sh/setup-uv from 5 to 7.

Release notes

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

v7.0.0 🌈 node24 and a lot of bugfixes

Changes

This release comes with a load of bug fixes and a speed up. Because of switching from node20 to node24 it is also a breaking change. If you are running on GitHub hosted runners this will just work, if you are using self-hosted runners make sure, that your runners are up to date. If you followed the normal installation instructions your self-hosted runner will keep itself updated.

This release also removes the deprecated input server-url which was used to download uv releases from a different server. The manifest-file input supersedes that functionality by adding a flexible way to define available versions and where they should be downloaded from.

Fixes

• The action now respects when the environment variable UV_CACHE_DIR is already set and does not overwrite it. It now also finds cache-dir settings in config files if you set them.
• Some users encountered problems that cache pruning took forever because they had some uv processes running in the background. Starting with uv version 0.8.24 this action uses uv cache prune --ci --force to ignore the running processes
• If you just want to install uv but not have it available in path, this action now respects UV_NO_MODIFY_PATH
• Some other actions also set the env var UV_CACHE_DIR. This action can now deal with that but as this could lead to unwanted behavior in some edgecases a warning is now displayed.

Improvements

If you are using minimum version specifiers for the version of uv to install for example

[tool.uv]
required-version = ">=0.8.17"

This action now detects that and directly uses the latest version. Previously it would download all available releases from the uv repo to determine the highest matching candidate for the version specifier, which took much more time.

If you are using other specifiers like 0.8.x this action still needs to download all available releases because the specifier defines an upper bound (not 0.9.0 or later) and "latest" would possibly not satisfy that.

🚨 Breaking changes

• Use node24 instead of node20 @​eifinger (#608)
• Remove deprecated input server-url @​eifinger (#607)

🐛 Bug fixes

• Respect UV_CACHE_DIR and cache-dir @​eifinger (#612)
• Use --force when pruning cache @​eifinger (#611)
• Respect UV_NO_MODIFY_PATH @​eifinger (#603)
• Warn when UV_CACHE_DIR has changed @​jamesbraza (#601)

🚀 Enhancements

• Shortcut to latest version for minimum version specifier @​eifinger (#598)

🧰 Maintenance

• Bump dependencies @​eifinger (#613)
• Fix test-uv-no-modify-path @​eifinger (#604)

... (truncated)

Commits

• 1e862df Wait 50ms before exit to fix libuv bug (#689)
• d7d33e1 chore: update known checksums for 0.9.10 (#681)
• 486d0b8 chore: update known checksums for 0.9.9 (#679)
• 5a7eac6 use old undici and ES2022 target for act support (#678)
• b49dc9e chore: update known checksums for 0.9.8 (#677)
• 30ce38e Correct description of cache-dependency-glob (#676)
• 0d20755 chore: update known checksums for 0.9.7 (#671)
• 8491d1d chore: update known checksums for 0.9.6 (#670)
• 8585678 Bump dependencies (#664)
• 22d500a Bump github/codeql-action from 4.30.8 to 4.30.9 (#652)
• 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.

[claude]

Claude finished @dependabot[bot]'s task —— View job

---

PR Review: Bump astral-sh/setup-uv from 5 to 7

Todo List

• Read and analyze changed workflow files
• Check for breaking change compatibility
• Review security implications
• Assess performance considerations
• Provide comprehensive feedback

Analysis of Changes

All five workflow files have been updated to use astral-sh/setup-uv@v7 instead of v5. The changes are straightforward version bumps:

Files Updated:

• .github/workflows/claude.yml:34 - Claude Code workflow
• .github/workflows/deploy-docs.yaml:36 - Documentation deployment
• .github/workflows/dragon-ai.yml:134 - Dragon AI agent workflow
• .github/workflows/main.yaml:35 - Main CI workflow
• .github/workflows/pypi-publish.yaml:37 - PyPI publishing workflow

Current Usage Pattern: All workflows use basic setup without deprecated features.

Review Findings

✅ Code Quality & Best Practices

• EXCELLENT: Clean, minimal configuration changes
• GOOD: Consistent pinning to major version (@v7) across all workflows
• GOOD: No deprecated server-url input found in any workflow

✅ Breaking Change Compatibility

• SAFE: Node.js 24 requirement is automatically handled by GitHub-hosted runners
• SAFE: No usage of deprecated server-url input that was removed in v7
• SAFE: All current configuration options remain compatible

✅ Security Considerations

• POSITIVE: v7 includes security improvements and bug fixes
• GOOD: No changes to permissions or token usage
• SAFE: Trusted action from reputable maintainer with regular updates

✅ Performance Improvements

• ENHANCEMENT: v7 includes performance optimizations for minimum version specifiers
• FIX: Improved cache handling with --force flag for pruning
• FIX: Better respect for UV_CACHE_DIR environment variable

⚠️ Minor Considerations

• INFO: Self-hosted runners (if any) need Node.js 24+ support
• INFO: v7 may display warnings if UV_CACHE_DIR is set by other actions

Recommendation

✅ APPROVE - This is a safe and beneficial upgrade that:

• Fixes several cache-related bugs
• Improves performance for version resolution
• Maintains full backward compatibility with current usage
• Enhances security and stability

The upgrade is well-tested by dependabot and ready for merge.

[claude]

Claude finished @dependabot[bot]'s task —— View job

---

PR Review: Bump astral-sh/setup-uv from 5 to 7

Todo List

• Read and analyze changed workflow files
• Check for breaking change compatibility
• Review security implications
• Assess performance considerations
• Provide comprehensive feedback

Analysis of Changes

All five workflow files have been updated to use astral-sh/setup-uv@v7 instead of v5. The changes are straightforward version bumps:

Files Updated:

• .github/workflows/claude.yml:34 - Claude Code workflow
• .github/workflows/deploy-docs.yaml:36 - Documentation deployment
• .github/workflows/dragon-ai.yml:134 - Dragon AI agent workflow
• .github/workflows/main.yaml:49 - Main CI workflow
• .github/workflows/pypi-publish.yaml:37 - PyPI publishing workflow

Current Usage Pattern: All workflows use basic setup without deprecated features.

Review Findings

✅ Code Quality & Best Practices

• EXCELLENT: Clean, minimal configuration changes
• GOOD: Consistent pinning to major version (@v7) across all workflows
• GOOD: No deprecated server-url input found in any workflow

✅ Breaking Change Compatibility

• SAFE: Node.js 24 requirement is automatically handled by GitHub-hosted runners
• SAFE: No usage of deprecated server-url input that was removed in v7
• SAFE: All current configuration options remain compatible

✅ Security Considerations

• POSITIVE: v7 includes security improvements and bug fixes
• GOOD: No changes to permissions or token usage
• SAFE: Trusted action from reputable maintainer with regular updates

✅ Performance Improvements

• ENHANCEMENT: v7 includes performance optimizations for minimum version specifiers
• FIX: Improved cache handling with --force flag for pruning
• FIX: Better respect for UV_CACHE_DIR environment variable

⚠️ Minor Considerations

• INFO: Self-hosted runners (if any) need Node.js 24+ support
• INFO: v7 may display warnings if UV_CACHE_DIR is set by other actions

Recommendation

✅ APPROVE - This is a safe and beneficial upgrade that:

• Fixes several cache-related bugs
• Improves performance for version resolution
• Maintains full backward compatibility with current usage
• Enhances security and stability

The upgrade is well-tested by dependabot and ready for merge.

---