dependabot[bot] opened a new pull request, #399: URL: https://github.com/apache/hudi-rs/pull/399
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 5 to 6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's releases</a>.</em></p> <blockquote> <h2>v6.2.1 ๐ Fix "No such file or directory version-manifest.json"</h2> <h2>Changes</h2> <p>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.</p> <h2>๐ Bug fixes</h2> <ul> <li>Look for version-manifest.json relative to action path <a href="https://github.com/eifinger"><code>@โeifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/456">#456</a>)</li> </ul> <h2>v6.0.0 ๐ activate-environment and working-directory</h2> <h2>Changes</h2> <p>This version contains some breaking changes which have been gathering up for a while. Lets dive into them:</p> <ul> <li><a href="https://github.com/astral-sh/setup-uv/blob/HEAD/#activate-environment">Activate environment</a></li> <li><a href="https://github.com/astral-sh/setup-uv/blob/HEAD/#working-directory">Working Directory</a></li> <li><a href="https://github.com/astral-sh/setup-uv/blob/HEAD/#default-cache-dependency-glob">Default <code>cache-dependency-glob</code></a></li> <li><a href="https://github.com/astral-sh/setup-uv/blob/HEAD/#use-default-cache-dir-on-self-hosted-runners">Use default cache dir on self hosted runners</a></li> </ul> <h3>Activate environment</h3> <p>In previous versions using the input <code>python-version</code> automatically activated a venv at the repository root. This led to some unwanted side-effects, was sometimes unexpected and not flexible enough.</p> <p>The venv activation is now explicitly controlled with the new input <code>activate-environment</code> (false by default):</p> <pre lang="yaml"><code>- name: Install the latest version of uv and activate the environment uses: astral-sh/setup-uv@v6 with: activate-environment: true - run: uv pip install pip </code></pre> <p>The venv gets created by the <a href="https://docs.astral.sh/uv/pip/environments/"><code>uv venv</code></a> command so the python version is controlled by the <code>python-version</code> input or the files <code>pyproject.toml</code>, <code>uv.toml</code>, <code>.python-version</code> in the <code>working-directory</code>.</p> <h3>Working Directory</h3> <p>The new input <code>working-directory</code> controls where we look for <code>pyproject.toml</code>, <code>uv.toml</code> and <code>.python-version</code> files which are used to determine the version of uv and python to install.</p> <p>It can also be used to control where the venv gets created.</p> <pre lang="yaml"><code>- name: Install uv based on the config files in the working-directory uses: astral-sh/setup-uv@v6 with: working-directory: my/subproject/dir </code></pre> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/setup-uv/commit/bd01e18f51369d5a26f1651c3cb451d3417e3bba"><code>bd01e18</code></a> Do not warn when version not in manifest-file (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/462">#462</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/c6a5ebaafeb1babe6b7402a384856f863ca8b1c7"><code>c6a5eba</code></a> chore: update known versions for 0.7.14 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/459">#459</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/790df8f465aaeefce9b567405434da4e5095bd2e"><code>790df8f</code></a> Revert "Set expected cache dir drive to C: on windows (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/451">#451</a>)" (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/460">#460</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/445689ea25e0de0a23313031f5fe577c74ae45a1"><code>445689e</code></a> Use latest version from manifest-file (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/458">#458</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/a02a550bdd3185dba2ebb6aa98d77047ce54ad21"><code>a02a550</code></a> Look for version-manifest.json relative to action path (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/456">#456</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/60cc2b45855283f89ec62f1aba5ee88bf9ec7fc7"><code>60cc2b4</code></a> Add input manifest-file (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/454">#454</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/7bbb36f4345bf059635fb6d04d0fb369ca42338e"><code>7bbb36f</code></a> chore: update known versions for 0.7.13 and 0.7.12 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/444">#444</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/60ecb381b4b43af6bb3f4debfa54d9b0b0107997"><code>60ecb38</code></a> Set expected cache dir drive to C: on windows (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/451">#451</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/252c9954247a3257f40af94d0d836d0ffb58f808"><code>252c995</code></a> chore: update known versions for 0.7.11 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/442">#442</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/477a814f2de90c2d4166598b37d04ac2f359284d"><code>477a814</code></a> chore: update known versions for 0.7.10 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/440">#440</a>)</li> <li>Additional commits viewable in <a href="https://github.com/astral-sh/setup-uv/compare/v5...v6">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
