v6.3.1 🌈 Do not warn when version not in manifest-file

Changes

This is a hotfix to change the warning messages that a version could not be found in the local manifest-file to info level.

A setup-uv release contains a version-manifest.json file with infos in all available uv releases. When a new uv version is released this is not contained in this file until the file gets updated and a new setup-uv release is made. We will overhaul this process in the future but for now the spamming of warnings is removed.

🐛 Bug fixes

• Do not warn when version not in manifest-file @​eifinger (#462)

🧰 Maintenance

• chore: update known versions for 0.7.14 @github-actions[bot] (#459)
• Revert "Set expected cache dir drive to C: on windows (#451)" @​eifinger (#460)

v6.3.0 🌈 Use latest version from manifest-file

Changes

If a manifest-file is supplied the default value of the version input (latest) will get the latest version available in the manifest. That might not be the actual latest version available in the official uv repo.

🚀 Enhancements

• Use latest version from manifest-file @​eifinger (#458)

v6.2.0 🌈 New input manifest-file

Changes

This release adds a new input manifest-file.

The manifest-file input allows you to specify a JSON manifest that lists available uv versions, architectures, and their download URLs. By default, this action uses the manifest file contained in this repository, which is automatically updated with each release of uv.

The manifest file contains an array of objects, each describing a version, architecture, platform, and the corresponding download URL.

You can supply a custom manifest file URL to define additional versions, architectures, or different download URLs. This is useful if you maintain your own uv builds or want to override the default sources.

For example:

[
  {
    "version": "0.7.12-alpha.1",
</tr></table>