Skip to content

Briosa 0.9.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Oct 23:07
· 55 commits to main since this release
v0.9.1
55d8762
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Briosa 0.9.1 is a compatible correction release for both independent SpatialAnalyzer targets, 2024.1.0508.5 and 2026.1.0529.7. The runtime contract stays at major 2 revision 0, so the 0.4.0 .NET, JavaScript/TypeScript, and Python clients work unchanged. Default operation admission is unchanged.

Corrections

  • Exact SDK argument labels. 13 labels (2026) and 12 (2024) that #227 changed away from exact-target evidence are restored. Examples: Object(s) instead of Objects, Show Toolkit?, Instrument's ID, Z Uncertainty), and Group To Fit (#256).
  • Delete Cloud Points by X Y Z Range is restored to its 0.8.0 behavior (#256). In 0.9.0 it sent the wrong MP step and sent omitted bounds as 0. It now sends the exact step and sets each bound only when it is supplied.
    • Important: this is a destructive, replay-unsafe operation that the default allowlist admits. In 0.9.0 it most likely failed outright; in 0.9.1 it can delete cloud points again.
    • The six bound arguments are at-risk: they have no licensed validation on 2024, and only a 2026 setter probe.
  • Vector-group reference lists. MakeCollectionVectorGroupNameRefListRuntimeSelect now returns its result instead of DataLoss after MP success. A guard test now fails the build if any operation declares an output kind the worker cannot retrieve (#257).
  • Vector percentages. GetVectorGroupProperties now reads tolerance percentages as doubles, so fractional values are no longer truncated (#257).
  • Typed reconnect errors. Reconnecting a connected generation that is not ready for commands, which is the default when no connected-SA attestation is configured, and supervisor state races now return typed lifecycle errors with recovery guidance instead of gRPC Unknown. Control Center reconnect actions now report the typed diagnostic instead of dropping the reply (#258).
  • 2024 interop fingerprint. 2024 packages 0.6.0 through 0.9.0 reported the 2026 interop fingerprint in GetServerInfo, offline diagnostics, and support bundles. 0.9.1 reports the 2024 target's own sha256:98F7CA51… (#255).

Hardening

  • The server reads appsettings.json from its package directory rather than the caller's working directory. Explicit content-root overrides still apply.
  • The worker pipe now verifies the OS-reported client process.
  • New fault tests cover unexpected response kinds, correlation mismatches, truncated frames, and worker exit on parent death (#259).

Release and CI validation (#254)

  • CI verifies committed interop artifacts again and runs the manual server startup tests.
  • Releases now require a commit on main and a version above every existing stable release.
  • Before packaging, releases repeat the full restore, interop, protocol (against the previous release), naming, and test gates.
  • Signing re-checks each package digest.

Validation

Portable CI and the release workflow ran the full server suites, package smoke, and the retained-client gate against the six published major-2 clients and twelve major-1 clients. 0.9.1 was not run against licensed SpatialAnalyzer. The corrected labels, the restored DeleteCloudPoints bounds, and the new output retrievals have no licensed validation.

Documentation corrections are in #260. Remediation tracking is in #233.

Full Changelog: v0.9.0...v0.9.1

Assets 20
Loading