Version Packages#495
Merged
Merged
Conversation
609d53e to
b9c4fe5
Compare
f1efeb6 to
1743141
Compare
coderdan
approved these changes
Jun 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@cipherstash/stack@0.18.0
Minor Changes
6e7ae4e: Export the operation classes returned by the encryption and DynamoDB clients as public API.
The classes returned from public methods are now exported and documented in the API reference, so their types can be named and their TSDoc links resolve.
@cipherstash/stack/encryption:EncryptOperation,EncryptQueryOperation,BatchEncryptQueryOperation,DecryptOperation,EncryptModelOperation,DecryptModelOperation,BulkEncryptOperation,BulkDecryptOperation,BulkEncryptModelsOperation,BulkDecryptModelsOperation.EncryptQueryOperationandBatchEncryptQueryOperationwere previously marked@internal; since they are returned fromEncryptionClient.encryptQuery, they are now public for consistency with the other operations.@cipherstash/stack/dynamodb:EncryptModelOperation,DecryptModelOperation,BulkEncryptModelsOperation,BulkDecryptModelsOperation.@cipherstash/stack/types:EncryptedQueryandEncryptedFromSchema.The
*WithLockContextvariants returned by.withLockContext()remain internal — they share the same awaitable shape and are not intended to be named directly.No runtime behaviour changes; this only widens the exported surface and corrects TSDoc cross-references that previously failed to resolve.
712d7fa: Fix: restore runtime null short-circuits in the encryption operation classes.
A prior refactor (
feat(stack): remove null from Encrypted type) tightened the type signatures to disallownulland, alongside that, deleted theif (value === null) return nullguards from every operation inpackages/stack/src/encryption/operations/. The type guard does not survive runtime: callers reaching the operation through a cast (e.g.null as any), dynamic model walking, or JS interop would then have their null silently encrypted by protect-ffi into a real SteVec ciphertext ({ k: 'sv', v: 2, ... }) — which is observable, surprising, and breaks symmetry with the model-helpers layer that does still treat null as "absent" at the field level.Restored, mirroring the pattern in
@cipherstash/protect:encrypt/encryptWithLockContext:if (plaintext === null) return null.bulkEncrypt/bulkEncryptWithLockContext: per-element null filter; nulls are preserved in position in the output.decrypt/decryptWithLockContext:if (encryptedData === null) return null.bulkDecrypt/bulkDecryptWithLockContext: per-element null filter, position-preserving merge.encryptQuery/encryptQueryWithLockContext:if (plaintext === null || plaintext === undefined) return { data: null }.batchEncryptQuery/batchEncryptQueryWithLockContext: per-element null/undefined filter; null slots in the input array stay null in the result array.Type adjustments to support the runtime behavior honestly:
BulkEncryptPayload['plaintext'],BulkEncryptedData['data'],BulkDecryptPayload['data'], and theTofBulkDecryptedDataall widen to... | null. Bulk APIs now accept and return mixed nullable arrays without filtering ahead of time.EncryptedQueryResultwidens to includenullso the batch query path can return position-stable arrays with null slots.Encryption.encrypt()andEncryption.decrypt()public signatures are unchanged — still narrow (JsPlaintext/Encryptedinput,Encrypted/JsPlaintextnon-nullable output). The runtime null short-circuit inEncryptOperation/DecryptOperationis defense in depth for callers reaching the operation classes through casts, dynamic field walking, or JS interop. The narrow-return contract holds for any caller that respects the input contract.@cipherstash/prisma-next@0.3.1
Patch Changes
@cipherstash/basic-example@1.2.12
Patch Changes
@cipherstash/prisma-next-example@0.0.4
Patch Changes
@cipherstash/bench@0.0.3
Patch Changes