Skip to content

fix(cli): scaffold EQL v3 encryption client from stash init #734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tobyhede merged 1 commit into from
Jul 21, 2026
+121 −157
Merged

fix(cli): scaffold EQL v3 encryption client from stash init #734

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions .changeset/init-placeholder-eql-v3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
'stash': patch
---

`stash init` now scaffolds an EQL **v3** encryption client, matching the EQL v3
database it installs.

The placeholder client (`DRIZZLE_PLACEHOLDER` / `GENERIC_PLACEHOLDER`) and the
introspection-driven client generator previously emitted EQL v2 authoring
patterns — `Encryption({ schemas })`, `encryptedColumn(...).equality().freeTextSearch()`,
and `encryptedType<T>('x', { equality: true })`. Since init installs a v3
database, this handed the customer's coding agent v2 guidance against a v3
schema (follow-up to #732 / #705).

Scaffolds now teach the v3 surface: `EncryptionV3` from `@cipherstash/stack/v3`,
the concrete-domain `types.*` factories (`types.TextSearch`, `types.IntegerOrd`,
`types.Text`, `types.Json`, …), and the `@cipherstash/stack-drizzle/v3` entry
(`extractEncryptionSchemaV3`) for Drizzle. The `encryptionClient` export shape
and the empty-schema "no schemas yet" error path are unchanged.
Loading
Loading