Skip to content

Releases

v0.5.2

Choose a tag to compare

@github-actions github-actions released this 08 Nov 20:39
56e1250

Changed

  • README: style fixes for the QSO Graph style guide (Google Developer Documentation Style Guide, American English).
  • README: install and rename steps with uv, in place of pip.

v0.5.1

Choose a tag to compare

@github-actions github-actions released this 29 Oct 15:28
3b3d9c2

Fixed

  • ADIF is read by qso_graph_lib.adif, the fleet's one ADI reader, which reads ADI as
    ADIF 3.1.7 defines it and passes ADIF's own test files. qsp-adif-convert and
    qsp_client.adif.reader had a scanner each, and they lost data:
    • reader.py looked for tags anywhere, values included, so a COMMENT containing
      <CALL:5>W9XYZ replaced the QSO's callsign.
    • Both read files in text mode, which turns CR LF into LF and breaks every multi-line
      field's declared length; qsp-adif-convert also dropped undecodable bytes
      (errors="ignore"), shifting every length after them. Files are now read with their
      line ends and bytes as written.
    • A file with no Header no longer has its first record's fields taken as the Header's.
      The functions and the converter's output are otherwise unchanged. New dependency:
      qso-graph-lib>=0.2.0 (standard library only).

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 18:19
cb840d9

Changed

  • Python 3.11 is the minimum. 3.10 reached end of life in October 2026
    (PEP 619), so it gets no further security
    releases on any platform. On Windows it was worse than unsupported: uv's 3.10
    is built against OpenSSL 1.1.1w, end of life since September 2023, so HTTPS
    from this server ran over an unmaintained TLS library. certifi does not help
    with that — it supplies the root store, not the implementation.

    3.10 support was already nominal. This package has linted with
    ruff target-version = "py311" and type-checked with mypy python_version = "3.11" for some time, so nothing ever verified the 3.10 claim.

    uv.lock is regenerated and the diff is large, but nothing is upgraded —
    it is the 3.10 resolution branch disappearing. Packages that carried two pins,
    one per Python branch, now carry the single 3.11+ pin they already resolved to.
    An install on 3.11 or later is unchanged.

Fixed

  • ci-all-green could not fail on the dependency audit. The audit job was
    added to its needs list on 2026-10-26 without the matching result check, and
    with if: always() the needs list gates nothing — the check script does. A
    lockfile advisory would have turned the audit red and left ci-all-green green:
    a gate that cannot fail, in the repository where two advisories had just been
    found. The result is now checked, as in the other 23.
  • The http:// check exempted 10. and 192.168. unanchored, so they matched
    anywhere in a line and http://example.com/api/v10.2/thing passed — verified
    with a planted file. Neither exemption protected anything: src/ holds exactly
    one http:// URL, the localhost default in config.py. The check is now the
    fleet's form, localhost/127.0.0.1/::1 only, and prints the offending line
    rather than only reporting that one exists. An exemption names the exact thing,
    never a prefix (.claude/rules/security.md).
  • The workflow actions move off Node 20: actions/checkout@v4 → @v5,
    actions/setup-python@v5 → @v6, astral-sh/setup-uv@v6 → @v7. The other 23
    repositories moved on 2026-10-26; this one was missed because it sits outside the
    fleet's repository selector — which is also how its missing Release page and its
    retired release flow went unnoticed.

v0.4.1

Choose a tag to compare

@KI7MT KI7MT released this 26 Oct 16:01
e378a65

Security

  • certifi in uv.lock moved from 2026.7.22 to 2026.10.23, clearing a CRITICAL
    advisory (GHSA-6q48-6c7w-9gw2). Nobody installing from PyPI was exposed:
    certifi arrives transitively through httpx with an open range and uv.lock
    is not in the wheel, so a fresh install always resolved a current certifi.
    What was exposed is anything running from this repository with
    uv sync --frozen, which includes this repository's own CI.
  • opentelemetry-api moved from 1.45.0 to 1.45.1, clearing CVE-2026-114603.
    Found by the new audit job below, not by Dependabot, which had not reported it:
    pip-audit reads the lockfile against an advisory database, and that is a
    different question from the one Dependabot's alert list answers.

Changed

  • A release is now a deliberate act, not a side effect of merging.
    publish.yml fires on workflow_dispatch with the version typed in, and
    merging into main publishes nothing. This was the last repository still on
    the develop → main → publish-on-merge flow that the 22 MCP servers left on
    2026-10-25; its develop was five commits behind main, so that branch had
    already stopped being where work landed. develop is gone.
  • CI audits the locked dependencies, per pull request and weekly. Its absence is
    why the certifi advisory above sat unnoticed: nothing read uv.lock against
    an advisory database. The weekly run matters because an advisory is published
    against a lockfile that has not changed, and no push or pull request fires then.
  • The one-off deprecate-qsp-mcp job is removed. The MCP Registry already
    reports io.github.qso-graph/qsp-mcp 0.1.1 as status=deprecated, so it is
    spent.

v0.4.0

Choose a tag to compare

@KI7MT KI7MT released this 26 Oct 16:01
cb39760
  • ADIF tools moved here from adif-mcp, which is now only the MCP server and ADIF's published
    resources. qsp-adif-convert converts an ADIF (.adi) log to JSON or NDJSON (it was
    adif-mcp convert); qsp_client.adif.reader reads .adi text and qsp_client.adif.models
    holds the QSO and entity models. They came with their tests. Nothing in the relay uses them.
  • qsp-adif-convert never drops a record silently (#24). A record it cannot convert used to
    vanish unless --errors was given, and the run still exited 0, so a log with no station
    callsign converted to [] and looked like success. It now always reports how many records
    failed and why on stderr, says to use --station-call when that is the reason, and exits 1.

v0.3.5

Choose a tag to compare

@KI7MT KI7MT released this 26 Oct 16:01
93fe702
  • ruff and mypy run in CI (qso-graph-devel#66), as a job the ci-all-green gate requires. This
    repo sat outside that rollout; it is in the MCP ecosystem and answers to the same rules as the
    servers. Settings follow adif-mcp, as everywhere else, and both run once rather than per Python
    version: they read the source, and neither answer changes with the interpreter.
  • _discover_tools builds rows of (server, namespaced name, tool), which is what
    mcp_to_openai_tools(namespace=True) documents and reads, but the list was annotated as holding
    two-tuples. Nothing produced or consumed that shape; the annotation was simply wrong.
  • BridgeConfig was imported into relay.py and never used, and two functions promised a dict
    and a str while returning whatever the JSON body held.
  • E501 is deferred rather than adopted (qso-graph-devel#70): what it reports in these repos are
    widths, not defects.

v0.3.4

Choose a tag to compare

@KI7MT KI7MT released this 26 Oct 16:01
f12e933
  • The published contact is maintainers@qso-graph.io (qso-graph-devel#69). The authors field
    carried a personal address, and that field is what PyPI shows on the package page. The project
    has had outside contributions; a project address is the fitting route for them.

v0.3.3

Choose a tag to compare

@KI7MT KI7MT released this 26 Oct 16:01
14c763c
  • Licence: GPL-3.0-or-later, as the LICENSE file already said. The package metadata and README said MIT; released versions up to 0.3.2 keep the MIT terms they were published with.

v0.3.2

Choose a tag to compare

@KI7MT KI7MT released this 26 Oct 16:01
504406f
  • PyPI: the Documentation link goes to this package's own page, https://qso-graph.io/servers/qsp-client/ (qso-graph/.github#15).
  • CI: the release flow (qso-graph/.github TEMPLATES.md). Work lands on develop; a release is a
    PR from develop into main, and merging it publishes to PyPI and the MCP Registry, verifies both
    and tags the release. CI runs on develop too, and PRs into main must come from develop or a
    security/ branch.

v0.3.1

Choose a tag to compare

@KI7MT KI7MT released this 26 Oct 16:01
5421c84

Fixed

  • Tool names are always valid function names (#8). When servers share a tool name (every
    qso-graph server has get_version_info), the copies are namespaced as server__tool, which
    0.3.0 already did. The server part comes from your config, though, so a name like my solar or
    9975.wspr could produce a function name that OpenAI or Gemini rejects, and so could a tool's
    own name (get version, solar.wind), which comes from a third-party server. Every exposed
    name is now cleaned to [A-Za-z0-9_-], starts with a letter or underscore, fits in 64
    characters, and stays unique even when two names clean to the same text; each still calls its
    server under its original name. Tests cover the namespacing, shared and unshared names, and the
    64-character limit with suffixes.