Repository navigation
QGSDK 0.1.1
Security
- QGSDK's own Python is 3.14.10 (was 3.13.16), for the eMudhra CA advisory: 3.13.16 and the pip it
carries still trust intermediate CAs with trivially weak keys. 3.13.18 is the fixed 3.13, but
QGSDK takes its Windows Python from python.org (the NuGet package), and python.org publishes no
Windows build of 3.13.18: 3.13 is in its source-only phase. 3.14.10 is on python.org for Windows
and on python-build-standalone for the rest, bundles pip 26.2.2, and is supported longer. Every download is checked against the SHA-256 its publisher lists. The locked tooling
list dropsbackports-zstd, needed only before 3.14. - CI asks for exact patch releases (3.11.18, 3.12.16, 3.13.18, 3.14.10) instead of "3.13", which
accepts whatever the runner already has.tests/test_pythons.pyfails a minor version or a patch
older than the advisory's, in the workflows and inmanifest.json.
Changed
- uv 0.13.6 in the
mcpprofile, the version the lab uses, so a server is built with the same uv
everywhere. Each download is checked against the SHA-256 uv publishes for it. (#21)
Unpack either archive and follow the README's setup for your platform. Check a download against SHA256SUMS; every file here was made by this repository's Release workflow, and GitHub signs that it was: gh attestation verify <file> -R qso-graph/qso-graph-sdk.