Repository navigation
Releases
QGSDK 0.1.2
Security
- soupsieve 4.1 (was 2.10) in the tooling QGSDK installs, for CVE-2026-126190, -126191 and
-126193. Nothing else inbootstrap/tooling-requirements.txtmoved.
Changed
- AGENTS.md and CLAUDE.md: the organization's shared agent guide.
- README: American spelling (license).
- The install checks reuse Desktop's downloaded sources.
tests/check.shand
tests/windows-check.ps1takeQGSDK_DESKTOP_CACHE, a folder carried between runs for Desktop's
vendor/.cache, and CI keeps it in the Actions cache. adif.org.uk is no longer asked on every run;
a slow answer from it had failed the Windows check.
Fixed
- The docs match what QGSDK installs. The
desktopprofile is named wherever the profiles are
listed (the package description, the Windows installer's help); its Windows tools include Perl and
MinGit, and on Linux it needs unzip and libatomic too. Linux arm64 is listed where it is supported,
the CI Pythons are 3.11 to 3.14, MinGit is 2.56.0.4, and the verify commands name the current release's files.
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.
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.
QGSDK 0.1.0
The first release.
Added
- Choose what you work on, and get exactly its tools. Three profiles:
desktop(QSO Graph
Desktop: Node.js, Rust, and Go and CMake for its FIPS crypto module),logger(QSO Graph Logger: Qt
and its compiler, CMake, Ninja, NSIS) andmcp(qso-graph's MCP servers: uv, Python 3.11 to 3.13,
git). The installer asks when none is given; running it again with another adds it. (#4, #11, #12) - Windows, Linux and macOS for every profile, Apple silicon and Intel; Linux arm64 (a Raspberry
Pi 5) for desktop and mcp. (#13) - What must come from the system is checked first and named, with the one command that installs
it: Microsoft's C++ Build Tools on Windows (desktop), the distribution's packages on Linux, Apple's
Xcode command-line tools on macOS. Nothing outside the prefix is touched. - Every profile is proven on every platform by
tests/check.shandtests/windows-check.ps1, run
by CI whenever the installer changes and weekly; the desktop check builds QSO Graph Desktop itself. - Releases (this one is the first): versioned archives, SHA256SUMS, and GitHub's signed record that
this repository's Release workflow made them. (#15)
Security
- The tooling QGSDK installs for itself was locked to certifi, brotli and setuptools versions with
published advisories (one critical); all three are upgraded, and CI now audits that lock. (#8, #9)
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.