Latest Results
Remove the stdin metadata from `uv check` (#20501)
Although it was a nice idea that it would simplify config contracts for
an mvp, Micha and I agreed it Simply Doesn't Work because in scanning a
workspace's files, ty is liable to find PEP-723 scripts, and then it
*definitely* needs to call back into uv anyway.
So, rather than include two modes, where one maybe works better in
simple workspaces with weird flags, we're going to just have the one
mode where ty calls back into uv.
This does mean we're preserving a bit of unfortunate redundancy, in that
we still need to do a sync to get the ty binary to invoke, and then ty
will turn around and ask for the sync again... but it's fine, if they
were going to be able to reuse the sync then it's gonna be a super cheap
resync.
The more notable "hole" this opens up is this command now takes various
cli flags that ty will not respect when it reinvokes uv. For the MVP we
are mostly just going with "that's fine, let's ship and iterate, it's
all in preview".
The most important settings to forward along should really be
persistently saved in config or env-vars, so common things will "just
work". The most important contradiction to this is IMO `--isolated`,
especially because we published some docs that suggested it with the
precommit hook, that's what https://github.com/astral-sh/uv/pull/20500
is for. Remove the stdin metadata from `uv check`
Although it was a nice idea that it would simplify config contracts for an mvp, Micha and I agreed it Simply Doesn't Work because in scanning a workspace's files, ty is liable to find PEP-723 scripts, and then it *definitely* needs to call back into uv anyway.
So, rather than include two modes, where one maybe works better in simple workspaces with weird flags, we're going to just have the one mode where ty calls back into uv.
This does mean we're preserving a bit of unfortunate redundancy, in that we still need to do a sync to get the ty binary to invoke, and then ty will turn around and ask for the sync again... but it's fine, if they were going to be able to reuse the sync then it's gonna be a super cheap resync.
The more notable "hole" this opens up is this command now takes various cli flags that ty will not respect when it reinvokes uv. For the MVP we are mostly just going with "that's fine, let's ship and iterate, it's all in preview".
The most important settings to forward along should really be persistently saved in config or env-vars, so common things will "just work". Latest Branches
0%
fix-preview-schema-fastjsonschema 0%
0%
renovate/taiki-e-install-action-2.x © 2026 CodSpeed Technology