@cipherstash/protect@5.2.0

Minor Changes

• 499c246: Implemented protectjs-ffi.

@cipherstash/protect@5.1.0

Minor Changes

• 5a34e76: Rebranded logging context and fixed tests.

@cipherstash/protect@5.0.0

Major Changes

• 76599e5: Rebrand jseql to protect.

@cipherstash/nextjs@2.1.0

Minor Changes

• 5a34e76: Rebranded logging context and fixed tests.

@cipherstash/nextjs@2.0.0

Major Changes

• 76599e5: Rebrand jseql to protect.

@cipherstash/nextjs@1.2.0

Minor Changes

• 3cb97c2: Added an optional argument to getCtsToken to fetch a new CTS token.

@cipherstash/nextjs@1.1.0

Minor Changes

• d0f5dd9: Enforced a check for the subject claims before setting cts session.

@cipherstash/nextjs@1.0.0

Major Changes

• 24f0a72: Implemented better error handling for fetching CTS tokens and accessing them in the Next.js application.

@cipherstash/jseql@4.0.0

Major Changes

• 5c08fe5: Enforced lock context to be called as a proto function rather than an optional argument for crypto functions.
  There was a bug that caused the lock context to be interpreted as undefined when the users intention was to use it causing the encryption/decryption to fail.
  This is a breaking change for users who were using the lock context as an optional argument.
  To use the lock context, call the withLockContext method on the encrypt, decrypt, and bulk encrypt/decrypt functions, passing the lock context as a parameter rather than as an optional argument.

@cipherstash/nextjs@0.12.0

Minor Changes

• 14c0279: Fixed optional response argument getting called in setCtsToken.