Skip to content

Commit 1cc4772

Browse files
committed
chore: changeset
1 parent ce381b8 commit 1cc4772

File tree

2 files changed

+9
-2
lines changed

2 files changed

+9
-2
lines changed

.changeset/fuzzy-memes-slide.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@cipherstash/protect": minor
3+
---
4+
5+
Released support for bulk encryption and decryption.

packages/protect/README.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -530,7 +530,8 @@ They automatically handle the mapping between your model's structure and the enc
530530

531531
### Bulk operations
532532

533-
Protect.js provides direct access to ZeroKMS bulk operations through the `bulkEncrypt` and `bulkDecrypt` methods. These methods are ideal when you need maximum performance and want to handle the correlation between encrypted/decrypted values and your application data manually.
533+
Protect.js provides direct access to ZeroKMS bulk operations through the `bulkEncrypt` and `bulkDecrypt` methods.
534+
These methods are ideal when you need maximum performance and want to handle the correlation between encrypted/decrypted values and your application data manually.
534535

535536
> [!TIP]
536537
> The bulk operations provide the most direct interface to ZeroKMS's blazing fast bulk encryption and decryption capabilities. Each value gets a unique key while maintaining optimal performance through a single call to ZeroKMS.
@@ -628,7 +629,8 @@ The `bulkDecrypt` method returns an array of objects with the following structur
628629

629630
#### Response structure
630631

631-
The `bulkDecrypt` method returns a `Result` object that represents the overall operation status. When successful from an HTTP and execution perspective, the `data` field contains an array where each item can have one of two outcomes:
632+
The `bulkDecrypt` method returns a `Result` object that represents the overall operation status.
633+
When successful from an HTTP and execution perspective, the `data` field contains an array where each item can have one of two outcomes:
632634

633635
- **Success**: The item has a `data` field containing the decrypted plaintext
634636
- **Failure**: The item has an `error` field containing a specific error message explaining why that particular decryption failed

0 commit comments

Comments
 (0)