chore(deps): bump astral-sh/setup-uv from 5 to 6

[dependabot]

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

Release notes

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

v6.6.0 🌈 Support for .tools-versions

Changes

This release adds support for asdf .tool-versions in the version-file input

🐛 Bug fixes

• Add log message before long API calls to GitHub @​eifinger (#530)

🚀 Enhancements

• Add support for .tools-versions @​eifinger (#531)

🧰 Maintenance

• Bump dependencies @​eifinger (#532)
• chore: update known versions for 0.8.12 @github-actions[bot] (#529)
• chore: update known versions for 0.8.11 @github-actions[bot] (#526)
• chore: update known versions for 0.8.10 @github-actions[bot] (#525)

v6.2.1 🌈 Fix "No such file or directory version-manifest.json"

Changes

Release v6.2.0 contained a bug that slipped through the automated test. The action tried to look for the default version-manifest.json in the root of the repostory using this action instead of relative to the action itself.

🐛 Bug fixes

• Look for version-manifest.json relative to action path @​eifinger (#456)

v6.0.0 🌈 activate-environment and working-directory

Changes

This version contains some breaking changes which have been gathering up for a while. Lets dive into them:

• Activate environment
• Working Directory
• Default cache-dependency-glob
• Use default cache dir on self hosted runners

Activate environment

In previous versions using the input python-version automatically activated a venv at the repository root. This led to some unwanted side-effects, was sometimes unexpected and not flexible enough.

The venv activation is now explicitly controlled with the new input activate-environment (false by default):

- name: Install the latest version of uv and activate the environment
  uses: astral-sh/setup-uv@v6
  with:
</tr></table> 

... (truncated)

Commits

• 557e51d Bump dependencies (#547)
• 1b46e13 Fix exclusions in cache-dependency-glob (#546)
• 26cf676 chore: update known versions for 0.8.14 (#543)
• 4e1e303 chore: update known versions for 0.8.13 (#536)
• 4959332 Bump dependencies (#532)
• adeb286 Add support for .tools-versions (#531)
• fce199e Add log message before long API calls to GitHub (#530)
• f758a4a chore: update known versions for 0.8.12 (#529)
• c0e7e93 chore: update known versions for 0.8.11 (#526)
• fda2399 chore: update known versions for 0.8.10 (#525)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

[holtskinner]

Breaking change for v6 shouldn't impact the publishing workflow

---

From Gemini

Upgrading astral-sh/setup-uv to v6: activate-environment Not Required for Your Workflow

For your specific workflow, which is designed to build and publish a Python package upon release, you do not need to add activate-environment: true. The uv build command is capable of handling the build process without requiring a pre-activated virtual environment.

The primary purpose of activating the environment within the CI job is to make the installed dependencies directly available on the PATH for subsequent commands. However, since your release-build job's only uv-related task is to run uv build, this activation is unnecessary. The build command will manage its own build dependencies.

The official documentation for astral-sh/setup-uv recommends against activating the environment for most use cases to avoid potential conflicts with other tools in the PATH.