v0.25.0
v0.25.0
⚠️ Breaking changes
- Removed
serviceTokenfromEncryptOptions,DecryptOptions, and the query option types. - Removed the
CtsTokenpublic type export. - Auth environment updated for stack-auth 0.36:
CS_REGIONis dropped in favour ofCS_WORKSPACE_CRN.
✨ Added
newClientnow accepts an optionalopts.strategy(anAuthStrategy,@cipherstash/auth-shaped object) on both Node and WASM. When supplied,getToken()is invoked on every ZeroKMS request. On WASM the strategy is required (no env/filesystem fallback); on Node it is optional and falls back to theAutoStrategybuilt from credentials / profile.
🔧 Fixed
- Node: capture a per-isolate Neon
Channelfor the JS-backed strategy, andunrefit so scripts can exit cleanly after a round trip. - Node: wrap the
getTokenJS call inContext::try_catchso a strategy that throws (or otherwise misbehaves) surfaces as a clean error instead of an unhandled rejection.
🧱 Changed
- Bumped
cipherstash-client,cts-common,stack-auth, andstack-profileto0.36.0. - Expanded integration coverage: JS-backed auth contract, event-loop-exit, and
newClientguard tests.
Upgrading: remove any serviceToken options and CtsToken imports; set CS_WORKSPACE_CRN instead of CS_REGION.
Full changelog: https://github.com/cipherstash/protectjs-ffi/blob/main/CHANGELOG.md