chore: release @nestm/crypto (alpha) - #3
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 20:11
5f6f413 to
6c858a7
Compare
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
1 participant
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@nestm/crypto@0.1.0-alpha.1
Minor Changes
@nestm/crypto/keys: X25519 keypair generation with raw/DER conversion, an HKDF-SHA256helper, and a recipient-addressed
sealTo/openFromprimitive (ephemeral-static X25519 →HKDF-SHA256 → AES-256-GCM) for wrapping an existing secret to a public key. The wire format is
version- and suite-tagged; the recipient public key is bound into the key schedule by the
library, the nonce is derived and never transmitted, callers may bind key-schedule
infoandAEAD
aad, and failures use the existingCryptoErrorcodes. Independent ofDataKeyProviderand
CipherEngine;@nestm/crypto/corestays free of NestJS, tenant, and cloud SDK imports.schema-agnostic Prisma write-encryption processor. Existing ciphertext is authenticated before
idempotent writes, batch resources are bounded, and the new persistence APIs never accept plaintext
data-encryption keys.