You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
stash eql install installs EQL's SQL into a customer database. After #1142, @cipherstash/eql carries two bundles: v3, for the TypeScript SDK's
cipherstash-client columns, and v4, for Stack Encrypt's (the Go SDK).
Problem
The CLI only knows v3. A Go project can't install v4, and a team moving from
TypeScript to Stack Encrypt needs both at once.
Proposal
Add --eql-version 3|4|all, defaulting to 3, which is today's behaviour. all is the documented way to migrate.
Make verify, status and the bundle-digest check aware of both bundles.
Add pty end-to-end tests.
Update skills/stash-cli, skills/stash-indexing and skills/stash-postgres in the same PR, and add a stash changeset.
The default changes to 4 later, announced in advance, once the
TypeScript SDK has moved to Stack Encrypt.
This issue is now part of #1694. Installing the EQL v4 bundle directly, with psql -f, drops the customer objects that use EQL. Those include policies, constraints, views, and generated columns.
Issue #1694 makes the CLI the supported way to install EQL v4. It adds the safe reinstall from #961 to the --eql-version 4 path here. Then it deprecates the direct install.
Activity
coderdan commentedon Nov 16, 2026
This issue is now part of #1694. Installing the EQL v4 bundle directly, with
psql -f, drops the customer objects that use EQL. Those include policies, constraints, views, and generated columns.Issue #1694 makes the CLI the supported way to install EQL v4. It adds the safe reinstall from #961 to the
--eql-version 4path here. Then it deprecates the direct install.