chore(release): 0.2.2#12
Merged
Merged
Conversation
Patch release marking the DEV-202 server-side FHE encryption migration. No public API or behavior change: the SDK is a thin REST client with no crypto, so moving encryption into the backend Lambda is transparent to consumers. Bundles the create() contract regression test added in #11. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Summary
Patch release 0.2.2 marking the DEV-202 server-side FHE encryption migration.
The SDK is a thin REST client with zero crypto, so moving FHE encryption into the backend Lambda (
FHE_MODE=local) is fully transparent to consumers — no public API or behavior change. This release simply cuts a clean version that bundles theinvoices.create()contract regression test (#11) guarding that migration.Changes
0.2.1→0.2.2.[0.2.2]entry (internal-only / no consumer impact).Release mechanics
After merge, tag
v0.2.2is pushed to triggerpublish.yml(lint → typecheck → test → build →npm publish --provenancevia OIDC trusted publisher).Part of Cost optimisation (DEV-198 / DEV-202).