Open
Conversation
…A-NeMo#950) Signed-off-by: Yuki Huang <yukih@nvidia.com>
…ngle node (NVIDIA-NeMo#898) Signed-off-by: Yuki Huang <yukih@nvidia.com>
Signed-off-by: Jimmy Zhang <jiemingz@nvidia.com> Signed-off-by: Jimmy Zhang <133159885+jiemingz@users.noreply.github.com> Signed-off-by: Sahil Jain <sahilj@nvidia.com> Co-authored-by: Sahil Jain <sahilj@nvidia.com> Co-authored-by: Sahil Jain <48468750+SahilJain314@users.noreply.github.com>
Signed-off-by: ashors1 <ashors@nvidia.com> Co-authored-by: Terry Kong <terrycurtiskong@gmail.com>
Signed-off-by: Tugrul Konuk <tkonuk@nvidia.com> Signed-off-by: Peter Jin <pjin@nvidia.com> Co-authored-by: Tugrul Konuk <tkonuk@nvidia.com>
Signed-off-by: Terry Kong <terryk@nvidia.com>
…VIDIA-NeMo#794) Signed-off-by: Felipe Vieira Frujeri <ffrujeri@nvidia.com>
Signed-off-by: Charlie Truong <chtruong@nvidia.com>
…NVIDIA-NeMo#970) Signed-off-by: Charlie Truong <chtruong@nvidia.com>
…#980) Signed-off-by: Felipe Vieira Frujeri <ffrujeri@nvidia.com>
…Mo#981) Signed-off-by: Felipe Vieira Frujeri <ffrujeri@nvidia.com>
Signed-off-by: Stanislav Kirdey <stan@inflection.ai> Signed-off-by: Stan Kirdey <stan@inflection.ai> Co-authored-by: Terry Kong <terrycurtiskong@gmail.com>
…IDIA-NeMo#926) Signed-off-by: Yubo Gao <yubog@nvidia.com> Co-authored-by: Shang Wang <samshang.wang@mail.utoronto.ca> Co-authored-by: Terry Kong <terrycurtiskong@gmail.com>
Signed-off-by: Zhanda <zhandazhu@gmail.com> Signed-off-by: Zhanda Zhu <49645678+zhandaz@users.noreply.github.com> Co-authored-by: Shang Wang <samshang.wang@mail.utoronto.ca>
Signed-off-by: Tugrul Konuk <tkonuk@nvidia.com> Signed-off-by: Peter Jin <pjin@nvidia.com> Co-authored-by: Tugrul Konuk <tkonuk@nvidia.com>
…VIDIA-NeMo#993) Signed-off-by: Terry Kong <terryk@nvidia.com>
Signed-off-by: Bogdan Salyp <bogdansalyp@gmail.com>
Signed-off-by: Yuki Huang <yukih@nvidia.com>
Signed-off-by: Yuki Huang <yukih@nvidia.com>
…#931) Signed-off-by: Charlie Truong <chtruong@nvidia.com>
…o#1012) Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: Terry Kong <terryk@nvidia.com>
Signed-off-by: Terry Kong <terryk@nvidia.com> Co-authored-by: Terry Kong <terryk@nvidia.com>
Signed-off-by: Julien Veron Vialard <jveronvialar@nvidia.com> Signed-off-by: Olivier Delalleau <507137+odelalleau@users.noreply.github.com> Signed-off-by: Terry Kong <terryk@nvidia.com> Co-authored-by: Olivier Delalleau <507137+odelalleau@users.noreply.github.com> Co-authored-by: Terry Kong <terrycurtiskong@gmail.com> Co-authored-by: Terry Kong <terryk@nvidia.com>
…#1001) Signed-off-by: Guyue Huang <guyueh@nvidia.com> Signed-off-by: Guyue Huang <140554423+guyueh1@users.noreply.github.com> Co-authored-by: Terry Kong <terrycurtiskong@gmail.com>
Signed-off-by: jubick1337 <mattyson.so@gmail.com> Signed-off-by: Matvei Novikov <mattyson.so@gmail.com>
Signed-off-by: Peter Jin <pjin@nvidia.com>
…eMo#1030) Signed-off-by: Charlie Truong <chtruong@nvidia.com>
…IDIA-NeMo#1046) Signed-off-by: ashors1 <ashors@nvidia.com>
terrykong
force-pushed
the
renovate/deps-dependency-updates
branch
7 times, most recently
from
5b48d73 to
205295b
Compare
terrykong
force-pushed
the
renovate/deps-dependency-updates
branch
6 times, most recently
from
4022c14 to
d9f03bc
Compare
terrykong
force-pushed
the
renovate/deps-dependency-updates
branch
7 times, most recently
from
e374f37 to
bf81049
Compare
terrykong
force-pushed
the
renovate/deps-dependency-updates
branch
8 times, most recently
from
de2e4b4 to
077b390
Compare
terrykong
force-pushed
the
renovate/deps-dependency-updates
branch
from
077b390 to
88b7eea
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4cb1d5d→b2dcbb68aa287d→cf57fdb76065f1→9fc9377v2→v6v4→v6v1→v3v5→v6v4→v7v5→v70.9.1→0.11.0v2→v3==2.8.1→==2.8.33.12→3.14.3v44.0.3→v46.1.6==2.8.0→==2.13.0==0.11.0→==0.18.0Release Notes
actions/checkout (actions/checkout)
v6Compare Source
v5Compare Source
v4Compare Source
v3Compare Source
actions/create-github-app-token (actions/create-github-app-token)
v3Compare Source
v2Compare Source
actions/setup-python (actions/setup-python)
v6Compare Source
actions/upload-artifact (actions/upload-artifact)
v7Compare Source
v6Compare Source
v5Compare Source
astral-sh/setup-uv (astral-sh/setup-uv)
v7Compare Source
v6Compare Source
astral-sh/uv (astral-sh/uv)
v0.11.0Compare Source
Released on 2026-03-23.
Breaking changes
This release includes changes to the networking stack used by uv. While we think that breakage will be rare, it is possible that these changes will result in the rejection of certificates previously trusted by uv so we have marked the change as breaking out of an abundance of caution.
The changes are largely driven by the upgrade of reqwest, which powers uv's HTTP clients, to v0.13 which included some breaking changes to TLS certificate verification.
The following changes are included:
rustls-platform-verifieris used instead ofrustls-native-certsandwebpkifor certificate verificationThis change should have no effect unless you are using the
native-tlsoption to enable reading system certificates.rustls-platform-verifierdelegates to the system for certificate validation (e.g.,Security.frameworkon macOS) instead of eagerly loading certificates from the system and verifying them viawebpki. The effects of this change will vary based on the operating system. In general, uv's certificate validation should now be more consistent with browsers and other native applications. However, this is the most likely cause of breaking changes in this release. Some previously failing certificate chains may succeed, and some previously accepted certificate chains may fail. In either case, we expect the validation to be more correct and welcome reports of regressions.In particular, because more responsibility for validating the certificate is transferred to your system's security library, some features like CA constraints or revocation of certificates via OCSP and CRLs may now be used.
This change should improve performance when using system certificate on macOS, as uv no longer needs to load all certificates from the keychain at startup.
aws-lcis used instead ofringfor a cryptography backendThere should not be breaking changes from this change. We expect this to expand support for certificate signature algorithms.
--native-tlsis deprecated in favor of a new--system-certsflagThe
--native-tlsflag is still usable and has identical behavior to--system-certs.This change was made to reduce confusion about the TLS implementation uv uses. uv always uses
rustlsnotnative-tls.Building uv on x86-64 and i686 Windows requires NASM
NASM is required by
aws-lc. If not found on the system, a prebuilt blob provided byaws-lc-syswill be used.If you are not building uv from source, this change has no effect.
See the CONTRIBUTING guide for details.
Empty
SSL_CERT_FILEvalues are ignored (for consistency withSSL_CERT_DIR)See #18550 for details.
Python
See the python-build-standalone release notes for details.
Enhancements
Preview features
--service-formatand--service-urltouv audit(#18571)Performance
Bug fixes
uv tool list --outdated(#18586)uv exportfor workspace member packages with conflicts (#18635)Documentation
FLASH_ATTENTION_SKIP_CUDA_BUILDguidance forflash-attninstalls (#18473)v0.10.12Compare Source
Released on 2026-03-19.
Python
Enhancements
--no-emit-package(#18565)Preview features
uv auditin the CLI help (#18540)Bug fixes
uv python list(#18459)Documentation
uv-docker-example(#18558)v0.10.11Compare Source
Released on 2026-03-16.
Enhancements
Performance
Bug fixes
--projectto refer to apyproject.tomldirectly and reduce to a warning on other files (#18513)SYSTEM_VERSION_COMPATwhen querying interpreters on macOS (#18452)uv sync --activerecreating active environments whenUV_PYTHON_INSTALL_DIRis relative (#18398)Documentation
-o requirements.txtinuv pip compileexample (#12308)v0.10.10Compare Source
Released on 2026-03-13.
Python
Enhancements
--outdatedflag touv tool list(#18318)--projectdirectory does not exist (#17714)uv init(#18417)uv cache clearan alias ofuv cache clean(#18420)uv_build(#18419)Preview features
uv auditoutput (#18392)uv audit(#18193)uv audit(#18394)Bug fixes
uv tool install --force(#18399)uv export(#18433)Content-Type(#18334)Documentation
v0.10.9Compare Source
Released on 2026-03-06.
Enhancements
fbgemm-gpu,fbgemm-gpu-genai,torchrec, andtorchtuneto the PyTorch list (#18338)uv_buildsettings withoutuv_build(#15750)/usr/lib/os-releaseon Linux system lookup failure (#18349)cargo auditableto include SBOM in uv builds (#18276)Configuration
UV_VENV_RELOCATABLE(#18331)Performance
Documentoverhead (#18306)Bug fixes
cp3-none-any(#17064)Documentation
v0.10.8Compare Source
Released on 2026-03-03.
Python
Enhancements
--exclude-newerfilters out all versions of a package (#18217)uv_builddirect build compatibility (#17902)Configuration
UV_INIT_BAREenvironment variable foruv init(#18210)Bug fixes
uv tool upgradefrom installing excluded dependencies (#18022)pylock.tomlfiles (#18227)--upgrade(#18226)uv treeorphaned roots and premature deduplication (#17212)Documentation
after_script(#18206)v0.10.7Compare Source
Released on 2026-02-27.
Bug fixes
Enhancements
v0.10.6Compare Source
Released on 2026-02-24.
Bug fixes
requires-pythonconflicting with.python-version(#18097)Documentation
v0.10.5Compare Source
Released on 2026-02-23.
Enhancements
uv lock --frozen(#17859)pylock.tomlwheels by tags andrequires-python(#18081)uv publish(#17783)exclude-newerinvalidates the lock file (#18100)Performance
Bug fixes
--no-emit-workspacewith--all-packageson single-member workspaces (#18098)UV_NO_DEFAULT_GROUPSrejecting truthy values like1(#18057)Documentation
uv exportformats (#17900)v0.10.4Compare Source
Released on 2026-02-17.
Enhancements
uv pythonerrors (#18008)Bug fixes
uv init / --name foo) (#17983)wheelandsdistfiles produced by theuv_buildbuild backend (#18020)v0.10.3Compare Source
Released on 2026-02-16.
Python
Enhancements
Preview features
exclude-newerinuv format(#17651)target-workspace-discoveryis enabled (#17965)uv format(#17977)Bug fixes
cpython-3.1is specified (#17972)--allow-existingwith minor version links on Windows (#17978)u64::MAXin version segments to prevent overflow (#17985)Documentation
v0.10.2Compare Source
Released on 2026-02-10.
Enhancements
Bug fixes
cargo-installfailing due to missinguv-testdependency (#17954)v0.10.1Compare Source
Released on 2026-03-19.
Python
Enhancements
--no-emit-package(#18565)Preview features
uv auditin the CLI help (#18540)Bug fixes
uv python list(#18459)Documentation
uv-docker-example(#18558)v0.10.0Compare Source
Since we released uv 0.9.0 in October of 2025, we've accumulated various changes that improve correctness and user experience, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes.
This release also includes the stabilization of preview features. Python upgrades are now stable, including the
uv python upgradecommand,uv python install --upgrade, and automatically upgrading Python patch versions in virtual environments when a new version is installed. Theadd-boundsandextra-build-dependenciessettings are now stable. Finally, theuv workspace diranduv workspace listutilities for writing scripts against workspace members are now stable.There are no breaking changes to
uv_build. If you have an upper bound in your[build-system]table, you should update it, e.g., from<0.10.0to<0.11.0.Breaking changes
Require
--clearto remove existing virtual environments inuv venv(#17757)Previously,
uv venvwould prompt for confirmation before removing an existing virtual environment in interactive contexts, and remove it without confirmation in non-interactive contexts. Now,uv venvrequires the--clearflag to remove an existing virtual environment. A warning for this change was added in uv 0.8.You can opt out of this behavior by passing the
--clearflag or settingUV_VENV_CLEAR=1.Error if multiple indexes include
default = true(#17011)Previously, uv would silently accept multiple indexes with
default = trueand use the first one. Now, uv will error if multiple indexes are marked as the default.You cannot opt out of this behavior. Remove
default = truefrom all but one index.Error when an
explicitindex is unnamed (#17777)Explicit indexes can only be used via the
[tool.uv.sources]table, which requires referencing the index by name. Previously, uv would silently accept unnamed explicit indexes, which could never be referenced. Now, uv will error if an explicit index does not have a name.You cannot opt out of this behavior. Add a
nameto the explicit index or remove the entry.Install alternative Python executables using their implementation name (#17756, #17760)
Previously,
uv python installwould install PyPy, GraalPy, and Pyodide executables with names likepython3.10into the bin directory. Now, these executables will be named using their implementation name, e.g.,pypy3.10,graalpy3.10, andpyodide3.12, to avoid conflicting with CPython installations.You cannot opt out of this behavior.
Respect global Python version pins in
uv tool runanduv tool install(#14112)Previously,
uv tool runanduv tool installdid not respect the global Python version pin (set viauv python pin --global). Now, these commands will use the global Python version when no explicit version is requested.For
uv tool install, if the tool is already installed, the Python version will not change unless--reinstallor--pythonis provided. If the tool was previously installed with an explicit--pythonflag, the global pin will not override it.You can opt out of this behavior by providing an explicit
--pythonflag.Remove Debian Bookworm, Alpine 3.21, and Python 3.8 Docker images (#17755)
The Debian Bookworm and Alpine 3.21 images were replaced by Debian Trixie and Alpine 3.22 as defaults in uv 0.9. These older images are now removed. Python 3.8 images are also removed, as Python 3.8 is no longer supported in the Trixie or Alpine base images.
The following image tags are no longer published:
uv:bookworm,uv:bookworm-slimuv:alpine3.21uv:python3.8-*Use
uv:debianoruv:trixieinstead ofuv:bookworm,uv:alpineoruv:alpine3.22instead ofuv:alpine3.21, and a newer Python version instead ofuv:python3.8-*.Drop PPC64 (big endian) builds (#17626)
uv no longer provides pre-built binaries for PPC64 (big endian). This platform appears to be largely unused and is only supported on a single manylinux version. PPC64LE (little endian) builds are unaffected.
Building uv from source is still supported for this platform.
Skip generating
activate.cshfor relocatable virtual environments (#17759)Previously,
uv venv --relocatablewould generate anactivate.cshscript that contained hardcoded paths, making it incompatible with relocation. Now, theactivate.cshscript is not generated for relocatable virtual environments.You cannot opt out of this behavior.
Require username when multiple credentials match a URL (#16983)
When using
uv auth loginto store credentials, you can register multiple username and password combinations for the same host. Previously, when uv needed to authenticate and multiple credentials matched the URL (e.g., when retrieving a token withuv auth token), uv would pick the first match. Now, uv will error instead.You cannot opt out of this behavior. Include the username in the request, e.g.,
uv auth token --username foo example.com.Avoid invalidating the lockfile versions after an
exclude-newerchange (#17721)Previously, changing the
exclude-newersetting would cause package versions to be upgraded, ignoring the lockfile entirely. Now, uv will only change package versions if they are no longer within theexclude-newerrange.You can restore the previous behavior by using
--upgradeor--upgrade-packageto opt-in to package version changes.Upgrade
uv formatto Ruff 0.15.0 (#17838)uv formatnow uses Ruff 0.15.0, which uses the 2026 style guide. See the blog post for details.The formatting of code is likely to change. You can opt out of this behavior by requesting an older Ruff version, e.g.,
uv format --version 0.14.14.Update uv crate test features to use
test-as a prefix (#17860)This change only affects redistributors of uv. The Cargo features used to gate test dependencies, e.g.,
pypi, have been renamed with atest-prefix for clarity, e.g.,test-pypi.Stabilizations
uv python upgradeanduv python install --upgrade(#17766)When installing Python versions, an intermediary directory without the patch version attached will be created, and virtual environments will be transparently upgraded to new patch versions.
See the Python version documentation for more details.
uv add --boundsand theadd-boundsconfiguration option (#17660)This does not come with any behavior changes. You will no longer see an experimental warning when using
uv add --boundsoradd-boundsin configuration.uv workspace listanduv workspace dir(#17768)This does not come with any behavior changes. You will no longer see an experimental warning when using these commands.
extra-build-dependencies(#17767)This does not come with any behavior changes. You will no longer see an experimental warning when using
extra-build-dependenciesin configuration.Enhancements
pyx.devas a target inuv authcommands despitePYX_API_URLdiffering (#17856)Bug fixes
v0.9.30Compare Source
Release Notes
Released on 2026-02-04.
Python
Enhancements
--extraoption (#17525)UV_HTTP_TIMEOUTerror message (#17493)Preview features
Bug fixes
uv publishwhen using pyx (#17832)Install uv 0.9.30
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.30/uv-installer.ps1 | iex"Download uv 0.9.30
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.9.29Compare Source
Release Notes
Released on 2026-02-03.
Python
Enhancements
uv version --bump devsimilar to pre-release bumps (#17796)uv publishserver errors (#17787)uv publishtrace logs (#17784)Preview features
baseanddefaultconda environment names (#17758)Bug fixes
PYTHONHOMEinheritance when spawning different Python versions (#17821)EqualStarandNotEqualStaroperators (#17751)system-configurationin sandboxes (#17829)Documentation
Security
--help(#17745)Install uv 0.9.29
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.29/uv-installer.ps1 | iex"Download uv 0.9.29