Merge pull request #69 from JPL-Devin/main

Bump python client

Author: HuiJun

CHANGELOG.md

@@ -507,6 +507,18 @@ literals rather than floats, and the tolerance applies to `Real` alone.
 - **Conformance harness**: two distinct ports are reserved, and a service that exits early is
   reported instead of waited on.
 
+### Python client (`opensysml` 0.3.2)
+
+- **The client changes in this release reach PyPI as 0.3.2**, once `opensysml-v0.3.2` is tagged:
+  the private service of its own, `MissingCapabilityError` for a service-side refusal, and the
+  three client fixes listed under Fixed. Installing the v0.3.0 core does not wait on it — the
+  published 0.3.1 takes an unpinned release's digest from the signed `SHA256SUMS.txt` it verifies
+  with sigstore — so this is the client's own changes reaching users, not a prerequisite for the
+  core release.
+- The `v0.3.0` digests are pinned after the core release's assets publish, before
+  `opensysml-v0.3.2` is tagged, so that release is verified against a committed digest rather
+  than against the manifest path alone.
+
 ### Project
 
 - **buf is the single source of protobuf codegen**, replacing ad-hoc `protoc` invocations: Go stubs

docs/project/roadmap.md

@@ -3,7 +3,7 @@
 Baseline: `main` @ `22f47533`, verified locally on 2026-08-26 with Go 1.25.0.
 Read `AGENTS.md` first; it governs everything below.
 
-0.2.1 is the newest release from `Open-MBEE/OpenSysML`, carrying `sysml`, `sysml-lsp` and
+0.3.0 is the newest release from `Open-MBEE/OpenSysML`, carrying `sysml`, `sysml-lsp` and
 `sysml-grpc` archives, and the Python client is on PyPI as `opensysml` 0.3.1. `main` carries what
 `CHANGELOG.md` lists as unreleased. Everything in "Release follow-through" is maintainer- or
 account-gated; everything after it is ordinary engineering work.
@@ -68,9 +68,10 @@ downloads the corpus (cached on the download script) and runs the suite with
 
 # Release follow-through
 
-Tagging a core release and publishing the Python client are both proven paths now: `v0.2.1` is
+Tagging a core release and publishing the Python client are both proven paths now: `v0.3.0` is
 released on `Open-MBEE/OpenSysML` with its full archive set, and `opensysml-v0.3.1` uploaded the
-client to PyPI, so `pip install opensysml` resolves. The procedure and its post-tag verification
+client to PyPI, so `pip install opensysml` resolves. The client declares 0.3.2, whose PyPI upload
+waits on the `opensysml-v0.3.2` tag. The procedure and its post-tag verification
 are in `docs/project/releasing.md`.
 
 ## R3 — Homebrew tap

python/opensysml/_version.py

@@ -6,4 +6,4 @@
 this value with the release tag before anything is uploaded.
 """
 
-VERSION = "0.3.1"
+VERSION = "0.3.2"

python/opensysml/binary.py

@@ -85,6 +85,13 @@
             'sysml-grpc-linux-arm64': '3451bb569c1c2993a5c648df27cadcec900d46e6e1d957f87aac979c8a16c9e5',
             'sysml-grpc-windows-amd64.exe': '3a630d38c2691a27c8f6e3b781f48e05b727c559b219b9c2e7bd8651c222628d',
         },
+        'v0.3.0': {
+            'sysml-grpc-darwin-amd64': '8c034172f604ec78c6c045b8eef0ddb2fdebac4f22852480ad3289a3e940cf14',
+            'sysml-grpc-darwin-arm64': 'c9f8fb0a424277cc83ab3f388e11e54fcc9328b9a2cb86a911e7b96fb6cb316a',
+            'sysml-grpc-linux-amd64': 'b39b720e020c325020af95c33640ad3583c938d74c40d29a0741fab6c03412de',
+            'sysml-grpc-linux-arm64': '2faeacdbc3dcd20053b2dc79b559bbbf2f53b7470d982b9908c7665a53b37462',
+            'sysml-grpc-windows-amd64.exe': 'f50f1b53008154c1a5fb39eb56f09464dedcf081037af765978304b2f33615c6',
+        },
     },
 }