Skip to content

Briosa 0.9.2

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 Oct 02:10
· 40 commits to main since this release
v0.9.2
c72e027
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.2 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 step text. 25 SA 2026 operations now send the SDK "View SDK Code" step text instead of installed-documentation text (#283, decision #246):

    • 13 punctuation or spacing changes, for example Save As..., Set SA's Window Pos with a straight apostrophe, (Rx,Ry,Rz), and two spaces before the hyphen in Export IGES File - Entire Model;
    • 12 letter-case changes.

    Both targets now send Make Pipe Relationship Cut. These steps have no licensed validation yet, so they are at-risk until the licensed probe session (#277) runs.

  • SDK exceptions no longer crash the worker. An exception from the SDK during an MP sequence now reports the phase that was proven, with a diagnostic code and no exception text (#282):

    • before ExecuteStep: not started;
    • during execution or result retrieval: outcome unknown;
    • in a getter after MP success: completed, with that output unavailable.

    Per-call faults keep the worker. Faults at the STA level still stop it. An SDK call fault before execution currently reports kind Internal, NotStarted, and DoNotReplay. A dedicated representation is tracked in #248.

Reliability and validation

  • All supervisor deadlines use the injected time provider: connect, execution watchdog, startup, readiness, heartbeat, shutdown, and cleanup. Production timeouts are unchanged. Timing-sensitive tests now run on virtual time instead of short real-clock budgets (#281).
  • A portable test checks every implemented SA 2026 binding against the committed exact-target evidence (MP step, argument labels, setter/getter family, and NOT_SUPPORTED entries). It carries 21 reviewed deviations (#284).
  • CI reports protobuf differences between the two exact targets and fails on any new same-number wire-type conflict. The one known conflict, ConstructObjectsFromSurfaceFacesRuntimeSelectRequest fields 1–2, is allowlisted pending a decision (#280).
  • An opt-in harness prepares the bounded licensed probe session. It is never run by ordinary builds or CI (#279).
  • Dependency updates: Google.Protobuf 3.36.2, Grpc 2.84, OpenTelemetry OTLP 1.19.1, coverlet 10.1.0, and current GitHub Actions.

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 the twelve major-1 clients. 0.9.2 was not run against licensed SpatialAnalyzer; the step-text corrections above remain at-risk.

Full Changelog: v0.9.1...v0.9.2

Assets 20
Loading