chore(python): update uv.lock after `trezorlib` release
What the developer wrote
Authored by Roman Zeyde
chore(python): update uv.lock after `trezorlib` release
[no changelog]
What changed, and why it matters
This is a routine build-file update that records a new release of Trezor's own Python library (trezorlib), bumping the version from 0.20.0 to 0.20.1. The change is in a lock file only and contains no code modifications. There is no security-relevant content visible in the commit.
No action required. Treat as normal maintenance. Review the separate `trezorlib` release notes for any security relevance if desired.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit updates uv.lock to reflect trezor package version 0.20.1 instead of 0.20.0, with source = { editable = "python" } unchanged. This is a dependency-lock synchronization after a trezorlib release. No source code, cryptographic, firmware, or API changes are present in the diff.
Changed components
uv.lockInspect captured patch +1 / −1
diff --git a/uv.lock b/uv.lock
index bf8c891f..1f72a352 100644
--- a/uv.lock
+++ b/uv.lock
@@ -2208,7 +2208,7 @@ wheels = [
[[package]]
name = "trezor"
-version = "0.20.0"
+version = "0.20.1"
source = { editable = "python" }
dependencies = [
{ name = "click" },
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.