Skip to content

v1.19.1 — Viya compatibility matrix and a Windows stdio fix

Latest
Latest

Choose a tag to compare

View all tags
@Criptic Criptic released this 30 Oct 18:44
v1.19.1
7a01837
This commit was signed with the committer’s verified signature.
Criptic David Weik
SSH Key Fingerprint: vJZwY5hUU2rXQYgmlYSxke/xNFJzwHNLZWUDtHduZ0k
Verified
Learn about vigilant mode.

A documentation release, with no server code changed. A new matrix shows which tools work on which SAS Viya release (#71). Stdio setups on Windows no longer fail to start after a git pull (#70, fixes #67).

Highlights

🧭 COMPATIBILITY.md: which tools work on which Viya release

COMPATIBILITY.md covers all 115 tools on every supported SAS Viya release:

  • LTS 2024.09, 2025.03, 2025.09 and 2026.03.
  • Stable 2026.07 to 2026.10.

Every call a tool can make was checked against the API specifications developer.sas.com publishes for each release, including conditional branches, retries and rollback calls. The README links the matrix from its prerequisites.

  • 109 of the 115 tools make no call that differs anywhere in that range.
  • Report authoring and management is limited on LTS 2024.09, whose Visual Analytics API has no copy or delete endpoints, no text or image objects, and fewer object types. This affects create_report, apply_report_operations, copy_report and delete_report.
  • export_report with format=summary needs 2026.03 or later.
  • Publishing a glossary term with update_glossary_term needs 2025.03 or later.
  • Every decisioning tool works on every release, including the 23 that are new in 1.19.0.

🪟 Stdio on Windows: start with uv run --no-sync

Plain uv run app-stdio first syncs .venv whenever it no longer matches uv.lock, as after a git pull. On Windows that sync fails with os error 32 if any copy of the server is still running from the same checkout. Common cases are two client entries, Claude Code and Claude Desktop side by side, or a test run. When the sync fails, the server does not start.

All stdio configurations in the README and examples/ now pass --no-sync. The README also adds the Claude Code CLI command and says to run uv sync after each git pull with the clients closed. TROUBLESHOOTING.md explains the error and how to check an environment that a failed sync left half-installed.

If your client configuration came from an earlier README, add --no-sync to its args, for example ["run", "--no-sync", "app-stdio"]. To update a checkout to this release:

  1. Close your MCP clients.
  2. Run git pull.
  3. Run uv sync.

🔢 Tool count

115 tools, unchanged: 57 read-only and 28 destructive.

🐳 Container image

ghcr.io/sassoftware/sas-mcp-server:1.19.1

Also published as 1.19, 1 and latest. The image is a rebuild with no server changes. The Helm chart is now 0.6.1 (appVersion 1.19.1); no chart values changed.

📄 Details

Assets 2
Loading