build(core): update `uv.lock` after #6247
What the developer wrote
Authored by Roman Zeyde
build(core): update `uv.lock` after #6247
[no changelog]
What changed, and why it matters
This is a routine build-system update that bumps the recorded version of an internal vendor package (tvl) from 2.2 to 2.3 in the Python lock file (uv.lock). The change itself is a single digit in a metadata file and contains no executable code changes, no security fixes, and no disclosed security relevance.
No security action required. Treat as normal build maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit updates uv.lock to reflect a version bump of the editable vendor package tvl (vendor/ts-tvl) from 2.2 to 2.3. This is a lock-file synchronization after a prior change (#6247). No source code, dependency URL, hash, or requirement specification is altered beyond the version string. No security content is present in the commit message or diff.
Changed components
core build lock file (uv.lock)vendor/ts-tvl package metadataInspect captured patch +1 / −1
diff --git a/uv.lock b/uv.lock
index 02bde72d6..c44a3e870 100644
--- a/uv.lock
+++ b/uv.lock
@@ -2279,7 +2279,7 @@ requires-dist = [
[[package]]
name = "tvl"
-version = "2.2"
+version = "2.3"
source = { editable = "vendor/ts-tvl" }
dependencies = [
{ name = "crcmod" },
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.