Repository navigation
Releases: spatialanalyzer/briosa-js
Release list
Briosa JavaScript/TypeScript 0.4.0
The 0.4.0 clients for both supported SpatialAnalyzer targets adopt Briosa runtime contract major 2. The three robot Machine ID requests now take collection/instrument identifiers, and overload failures retain their typed execution and replay evidence. Upgrade to the matching Briosa Server 0.9.0 when it is published; these packages do not select major-1 servers.
Both registry packages were built and published from merged source 3f8c87c6a9ce643e7945c5d49ea52469eba32263 by the protected release workflow. Package conformance used a fake SDK; no licensed SpatialAnalyzer client run is claimed.
0.3.0: Clean MP argument names
The JavaScript/TypeScript 0.3.0 clients remove explanatory parenthetical text from public MP argument and result names for both supported SpatialAnalyzer targets. Qualifier notes remain in documentation, including the meaning of zero tolerance. All names in the four collision-exception methods remain unchanged.
Source/JSON migration: update named arguments, properties, object keys, and reflection lookups when upgrading. See the complete migration guide. Binary field identities and runtime contract 1.0 are unchanged.
Packages consume the verified, published Briosa Server 0.8.0 protocol:
Validation: the publishing workflow passed the complete target matrix. Actual registry downloads were installed into isolated consumers; both products passed 12 fake-SDK scenarios against each released Server 0.6.1, 0.7.0, and 0.8.0 (72 scenario runs). No licensed SpatialAnalyzer validation was performed for this release.
Briosa JavaScript/TypeScript 0.2.0
Briosa JavaScript/TypeScript 0.2.0
Client 0.2.0 adds offline, per-application selection of compatible Briosa installations for the package's exact SpatialAnalyzer target.
- Discover Registry64 registrations, committed stores, and explicit search roots; select the highest compatible stable server.
- Select an installation ID, executable path, exact version, or narrower version range explicitly. Invalid explicit choices fail without fallback.
- Require behavioral contract major 1, revision 0 or newer; support the exact published Server 0.6.1 through a separately tested legacy exception.
- Verify the running server against the selected installation before SDK or SA activity, and retain that selection for the session.
- Keep exact protocol generation pins to published Server 0.7.0 while allowing compatible runtime server versions.
Migration: BRIOSA_SERVER_PATH is ignored by default in 0.2. Use per-application selection options, or explicitly opt in to the legacy environment override. Previously published 0.1.0 and 0.1.1 packages retain their original exact server pins.
Installer 0.3.0 can register custom stores. Installing multiple SA releases does not establish safe concurrent execution or change SDK registration. Exact activated-SDK identity, connected-SA identity, readiness, process ownership, and no-replay rules remain enforced.
Portable validation covers both exact targets against packaged Servers 0.6.1 and 0.7.0 with a fake SDK. This release does not add licensed SpatialAnalyzer validation.
Packages:
Target-specific usage and migration · Shared compatibility contract
Client 0.1.1 for Briosa Server 0.6.1
Client 0.1.1 pairs with Briosa Server 0.6.1 for each exact SpatialAnalyzer target. Client 0.1.0 required Server 0.6.0 and rejected the security-patched server. This patch updates the verified protocol/conformance artifacts and exact server identity; public schemas and operation bindings are unchanged.
Install the matching Server 0.6.1 distribution. Package names remain exact-target; application namespaces/imports remain stable. Compatibility checks still require server source revision 32a3b56ba4ae31ea5ec6ec3b2aa051eb61c866aa and the package's exact SA target.
The publishing workflow passed protocol drift checks, unit tests, the portable client conformance suite, formatting/lint checks, packaging, and installed-package consumers for both targets. After publication, clean consumers downloaded both packages from their public registry and verified version 0.1.1, exact target, Server 0.6.1 identity, and stable public imports without starting SpatialAnalyzer.
No licensed-SA or enterprise deployment validation is claimed by this release. Those existing v1.0 gates remain outstanding.
Refs #27 and briosa#208.
Briosa JavaScript / TypeScript clients v0.1.0
Initial JavaScript / TypeScript client packages for the independent SA 2024.1.0508.5 and SA 2026.1.0529.7 products.
Packages
Package names identify the exact SpatialAnalyzer release; client version 0.1.0 is independent of the pinned Briosa Server 0.6.0. Application code retains import ... from 'briosa' with an npm alias. Select one target per application environment.
Validation and Publishing
- Release build and validation passed both target jobs, including protocol drift, conformance, tests, package identity, and packaged-consumer checks.
- Both packages were installed from npm into separate clean consumer environments. Package versions, target identities, and the stable public namespace/import were verified without starting SpatialAnalyzer.
- The initial npm uploads used the exact archives from the successful release build and authenticated local publishing. They do not have GitHub OIDC provenance. Package-specific GitHub trusted publishers are configured for subsequent releases.
See RELEASING.md for the release procedure.
Remaining Validation
Protected licensed-SA runtime CI and representative enterprise Artifactory validation remain outstanding. This v0.x release does not establish that every MP operation or deployment environment has been exercised. A separately installed and licensed exact-target SpatialAnalyzer environment is required for MP execution.