Version Packages

[github-actions]

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.

Releases

@cipherstash/stack-prisma@1.3.0

Minor Changes

• ae63dcd: Move the bundled EQL v3 migrations to eql-3.1.0. EQL 3.1.0 is a minor
  release for the Rust eql-bindings crate. Its install SQL changes only the
  version stamp: eql_v3.version() returns '3.1.0' and the eql_v3 schema
  comment reads '3.1.0'. No function, operator, domain or index behaviour
  changes.

  Two artefacts carry the new bundle:

  • A new upgrade edge, 20261005T0000_upgrade_eql_v3_3_1_0, carrying the
    invariant cipherstash:upgrade-eql-v3-bundle-3.1.0-v1. Existing databases
    re-install through it on the next prisma-next migration plan followed by
    prisma-next migrate. migrate alone is not enough: only
    migration plan copies the new directory into your repo.
  • The baseline install migration 20260601T0100_install_eql_v3_bundle, which
    now bakes 3.1.0 and gains a sixth op, a no-SQL carrier for the new
    invariant, so fresh databases land on 3.1.0 from the single all-additive
    genesis edge and db init keeps working.

  A 1.2.x database walks one edge. A 1.0.0 or 1.1.x database walks three.
  1.2.x shipped eql-3.0.6, so migrate walks only the 3.1.0 edge. 1.0.0 and
  1.1.x shipped eql-3.0.4, so migrate walks the 3.0.5, 3.0.6 and 3.1.0 edges in
  one transaction, re-installing the ~2.6 MB bundle three times. As with every EQL
  upgrade, each re-install opens with DROP SCHEMA IF EXISTS eql_v3 CASCADE:
  re-run your grant script, and recreate functional indexes and anything else
  depending on eql_v3.

  Action required, including on 1.2.x: the baseline changed again. 1.2.0
  and 1.2.1 shipped the baseline at eql-3.0.6, and this release changes those
  published bytes. 1.0.0 to 1.1.1 shipped it at eql-3.0.4. If your project has a
  migrations/cipherstash/ directory generated against any earlier version,
  delete it and re-run prisma-next migration plan:

  rm -rf migrations/cipherstash
  npx prisma-next migration plan

  Your database keeps its markers, so already-applied invariants are not re-run.
  If you skip the delete, a fresh db init from a 1.2.x directory refuses with
  Operation cipherstash.upgrade-eql-v3-bundle-3.1.0 has class "data" which is not allowed by policy. From a 1.0.0 or 1.1.x directory it refuses on the 3.0.5
  edge instead. See "Upgrading from 1.0.0, 1.1.x or 1.2.x" in the package README.

  Why the baseline was re-emitted rather than given a second genesis edge.
  The 3.0.5 and 3.0.6 entries said this trade must be re-argued on adoption
  numbers at each bump. Unlike the 3.0.6 re-emit, this one changes a published
  baseline. The team chose it on these numbers: @cipherstash/stack-prisma had
  481 npm downloads in the 30 days to 3 October 2026, and 384 in the last 7 of
  those days, 305 of them on the 1.2.0 release day. The append-only alternative,
  a second from: null genesis edge, would add another permanent ~2.6 MB copy of
  the bundle for a release that changes no SQL behaviour.

Patch Changes

• Updated dependencies [c851db5]
  • @cipherstash/eql@3.1.0
  • @cipherstash/stack@1.3.0

@cipherstash/eql@3.1.0

Minor Changes

• c851db5: Rust TextEq and TextEqQuery support Stack Encrypt's target-directed API behind the stack-encrypt feature. The stored table and column identifier supplies the encryption context; native ciphertext and equality terms are transcoded into EQL payloads while Vitamin C owns plaintext encoding. This is a new producer profile with exact string equality, independent of existing cipherstash-client ciphertext and terms. Query operands carry no recoverable ciphertext.

stash@1.3.0

Patch Changes

• ae63dcd: skills/stash-prisma: the stale-migrations/cipherstash/ table now describes
  eql-3.1.0. The baseline bakes 3.1.0, 1.2.x shipped 3.0.6, and the table names
  the db init refusal a stale 1.2.x directory produces.
• Updated dependencies [c851db5]
• Updated dependencies [f7f1c76]
  • @cipherstash/eql@3.1.0
  • @cipherstash/migrate@1.0.1

@cipherstash/migrate@1.0.1

Patch Changes

• f7f1c76: The package's source links now point at its folder under
  languages/typescript/ in cipherstash/stack. The previous release linked to
  its old folder under packages/, which no longer exists, so the README's
  source links and the npm page's repository link returned 404.

@cipherstash/nextjs@4.4.1

Patch Changes

• f7f1c76: The package's source links now point at its folder under
  languages/typescript/ in cipherstash/stack. The previous release linked to
  its old folder under packages/, which no longer exists, so the README's
  source links and the npm page's repository link returned 404.

@cipherstash/protect-ffi@0.33.1

Patch Changes

• f7f1c76: The package's source links now point at its folder under
  languages/typescript/ in cipherstash/stack. The previous release linked to
  its old folder under packages/, which no longer exists, so the README's
  source links and the npm page's repository link returned 404.

@cipherstash/protect-ffi-darwin-arm64@0.33.1

Patch Changes

• f7f1c76: The package's source links now point at its folder under
  languages/typescript/ in cipherstash/stack. The previous release linked to
  its old folder under packages/, which no longer exists, so the README's
  source links and the npm page's repository link returned 404.

@cipherstash/protect-ffi-darwin-x64@0.33.1

Patch Changes

• f7f1c76: The package's source links now point at its folder under
  languages/typescript/ in cipherstash/stack. The previous release linked to
  its old folder under packages/, which no longer exists, so the README's
  source links and the npm page's repository link returned 404.

@cipherstash/protect-ffi-linux-arm64-gnu@0.33.1

Patch Changes

• f7f1c76: The package's source links now point at its folder under
  languages/typescript/ in cipherstash/stack. The previous release linked to
  its old folder under packages/, which no longer exists, so the README's
  source links and the npm page's repository link returned 404.

@cipherstash/protect-ffi-linux-x64-gnu@0.33.1

Patch Changes

• f7f1c76: The package's source links now point at its folder under
  languages/typescript/ in cipherstash/stack. The previous release linked to
  its old folder under packages/, which no longer exists, so the README's
  source links and the npm page's repository link returned 404.

@cipherstash/protect-ffi-linux-x64-musl@0.33.1

Patch Changes

• f7f1c76: The package's source links now point at its folder under
  languages/typescript/ in cipherstash/stack. The previous release linked to
  its old folder under packages/, which no longer exists, so the README's
  source links and the npm page's repository link returned 404.

@cipherstash/protect-ffi-win32-x64-msvc@0.33.1

Patch Changes

• f7f1c76: The package's source links now point at its folder under
  languages/typescript/ in cipherstash/stack. The previous release linked to
  its old folder under packages/, which no longer exists, so the README's
  source links and the npm page's repository link returned 404.

@cipherstash/stack@1.3.0

Patch Changes

• Updated dependencies [f7f1c76]
  • @cipherstash/protect-ffi@0.33.1

@cipherstash/stack-drizzle@1.3.0

Patch Changes

• @cipherstash/stack@1.3.0

@cipherstash/stack-supabase@1.3.0

Patch Changes

• @cipherstash/stack@1.3.0

@cipherstash/wizard@1.3.0

@cipherstash/e2e@0.0.8

Patch Changes

• Updated dependencies [ae63dcd]
  • stash@1.3.0
  • @cipherstash/stack@1.3.0
  • @cipherstash/wizard@1.3.0

@cipherstash/basic-example@1.2.19

Patch Changes

• @cipherstash/stack@1.3.0
• @cipherstash/stack-drizzle@1.3.0

@cipherstash/prisma-example@0.1.5

Patch Changes

• Updated dependencies [ae63dcd]
  • @cipherstash/stack-prisma@1.3.0
  • @cipherstash/stack@1.3.0

@cipherstash/bench@0.0.10

Patch Changes

• @cipherstash/stack@1.3.0
• @cipherstash/stack-drizzle@1.3.0

@cipherstash/ffi-integration-tests@1.0.3

Patch Changes

• Updated dependencies [f7f1c76]
  • @cipherstash/protect-ffi@0.33.1

@cipherstash/test-kit@0.0.6

Patch Changes

• @cipherstash/stack@1.3.0

[auxesis]

Fix for failing build is #1081.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: da5832fb-836c-4f31-a2f0-52b903f2b9a6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}