Releases: cipherstash/protectjs
Releases · cipherstash/protectjs
@cipherstash/protect@9.3.0
Minor Changes
- 01fed9e: Added audit support for all protect and protect-dynamodb interfaces.
@cipherstash/protect-dynamodb@1.0.0
@cipherstash/protect-dynamodb@0.3.0
@cipherstash/protect@9.2.0
Minor Changes
- 587f222: Added support for deeply nested protect schemas to support more complex model objects.
@cipherstash/protect-dynamodb@0.2.0
Minor Changes
- 5fc0150: Fix build and publish.
@cipherstash/protect@9.0.0
Major Changes
-
1bc55a0: Implemented a more configurable pattern for the Protect client.
This release introduces a new
ProtectClientConfigtype that can be used to configure the Protect client.
This is useful if you want to configure the Protect client specific to your application, and will future proof any additional configuration options that are added in the future.import { protect, type ProtectClientConfig } from "@cipherstash/protect"; const config: ProtectClientConfig = { schemas: [users, orders], workspaceCrn: "your-workspace-crn", accessKey: "your-access-key", clientId: "your-client-id", clientKey: "your-client-key", }; const protectClient = await protect(config);
The now deprecated method of passing your tables to the
protectclient is no longer supported.import { protect, type ProtectClientConfig } from "@cipherstash/protect"; // old method (no longer supported) const protectClient = await protect(users, orders); // required method const config: ProtectClientConfig = { schemas: [users, orders], }; const protectClient = await protect(config);
@cipherstash/protect@8.4.0
Minor Changes
- a471821: Fixed a bug in the model interface to correctly handle undefined and null values.
@cipherstash/protect@8.3.0
Minor Changes
- 628acdc: Implemented createSearchTerms for a streamlined way of working with encrypted search terms.
@cipherstash/protect@8.2.0
Minor Changes
- 0883e16: Fix cipherstash.toml and cipherstash.secret.toml file loading by bumping to @cipherstash/protect-ffi v0.14.2