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/auth@1.0.0

Minor Changes

• fd0ee91: OidcFederationStrategy now keeps one CTS token per distinct provider JWT
  instead of one token for everyone. getJwt is called on every getToken()
  and must return the JWT of the user the current request is for; a JWT is
  exchanged once and its CTS token reused while that token is valid and the
  JWT's entry is still in the bounded least-recently-used cache (eviction before
  expiry, or cacheCapacity: 0, means another exchange; see below). Previously
  the strategy cached the first user's token and handed it to
  every caller until it expired, so on a server serving many users through one
  client a value one user encrypted under a lock context could be bound to
  another user's identity (stack-auth OidcFederationStrategy reuses one user's token for every user until it expires — lock context can bind to the wrong person #1045).

  getToken() now calls getJwt in the caller's own async context and hands the
  JWT to a new getTokenForJwt(jwt) method, on both the Node and wasm-inline
  entries. Previously the Node binding ran getJwt through a napi threadsafe
  function, in the async context of create(), so a callback that read the
  request from AsyncLocalStorage (Clerk's auth(), Next.js headers()) saw
  no request from a module-level strategy, or the creating request from one
  created inside a request. One long-lived strategy now serves every user from
  such a callback. getTokenForJwt is also public, for a caller that already
  holds the user's JWT; it shares the strategy's cache with getToken().

  A token persisted through createWithStore (for example a cookie) is now
  served only to the JWT it was federated from, so a store shared across users,
  or a cookie left over from a previous sign-in, is a cache miss rather than
  another user's token. The store is still one slot, so a store shared by
  several users caches only the most recent of them; give each user their own
  (a per-browser cookie already is). The stored JSON carries a new
  federated_from field; tokens stored by earlier releases have none and are
  re-federated once.

  Because the cache is keyed on the whole JWT, an identity provider that rotates
  JWTs faster than the CTS token lifetime (about 15 minutes) re-federates on each
  rotation, where earlier releases reused the stored token.

  The cache holds 1024 JWTs unless told otherwise. create and createWithStore
  take an optional cacheCapacity after baseUrl (the cacheCapacity option on
  @cipherstash/auth/wasm-inline); when the cache is full the least recently
  used JWT's token is dropped, that user is exchanged again on their next call,
  and the eviction is logged at debug. 0 caches nothing. Existing calls are
  unchanged.

Patch Changes

• fb75f40: Auth failures carry more help, and their messages never quote a credential or another library's text. A failure's type (NOT_AUTHENTICATED, INVALID_CRN, ...) is unchanged.

  • REQUEST_ERROR's message no longer repeats the transport's own error, which can carry a URL with its query string. It gains help saying what to check.
  • INVALID_TOKEN for a token whose claims do not decode no longer quotes the decoder's message, which could carry a byte or a claim of the token.
  • A failed device binding reports ZeroKMS's status, not its response body.
  • SERVER_ERROR for a refused token exchange names the HTTP status and the auth server's error_description, not the response body, which from the edge in front of it is an HTML page and can echo the access key. A body that is not JSON is reported by where it broke, not by the parser's message.
  • A profile file that is not valid JSON is reported by error kind, line and column, not by the parser's message, which could quote the file.
  • INVALID_GRANT, INVALID_WORKSPACE_ID and ALREADY_CONSUMED gain help, and NOT_AUTHENTICATED's help names stash auth login.
  • A STORE_ERROR carries the help of the profile failure underneath it, such as logging in again when the profile file is missing.
  • @cipherstash/auth-darwin-x64@1.0.0
  • @cipherstash/auth-darwin-arm64@1.0.0
  • @cipherstash/auth-win32-x64-msvc@1.0.0
  • @cipherstash/auth-linux-x64-gnu@1.0.0
  • @cipherstash/auth-linux-arm64-gnu@1.0.0
  • @cipherstash/auth-linux-x64-musl@1.0.0

@cipherstash/stack@1.3.0

Minor Changes

• bbb1bfa: encrypt on a types.Json column now types its result as Encrypted | null when the plaintext may be null. A null document has always resolved to { data: null } at runtime (it is stored as SQL NULL, not encrypted), but the result was typed Encrypted, so result.data.c compiled and then threw. encrypt is now generic over the plaintext's type: a literal null, or a value typed JsonDocument, gives data: Encrypted | null, through .withLockContext() and .audit() too. A value TypeScript knows is non-null, and every scalar column, still gives data: Encrypted. No runtime change. If your code reads result.data after encrypting a Json value that may be null, it must now check for null first. EncryptOperation and EncryptOperationWithLockContext take an optional result type parameter (default Encrypted), and the EncryptResult<P> helper type is exported from @cipherstash/stack/encryption.

  @cipherstash/stack-supabase: the per-term query-encryption fallback (used when the client has no bulkEncrypt) now rejects a null envelope instead of sending the string "null" as a filter operand, matching the bulk path.

  stash: the stash-encryption skill now says what encrypt returns for a null Json document.

Patch Changes

• fd0ee91: Document how OidcFederationStrategy serves many users through one client: the
  getJwt callback runs on every operation, in the caller's async context, and
  must return the JWT of the user behind the current request, and each user's
  JWT is exchanged for that user's own token (stack-auth's fix for
  stack-auth OidcFederationStrategy reuses one user's token for every user until it expires — lock context can bind to the wrong person #1045). One caveat is documented for the @cipherstash/stack
  client on the native entry, which calls the strategy from a background task so
  a request read from AsyncLocalStorage is not visible inside getJwt there
  yet: capture the request in the closure or build the client per request until
  @cipherstash/stack runs a second encryption engine (protect-ffi) — new major built on stack-encrypt (umbrella) #1065 lands. The docs and the stash-auth, stash-encryption,
  stash-supabase and stash-edge skills say so, and say that on earlier
  @cipherstash/auth releases a strategy caches one token for everyone, so a
  client there must serve one user.
• 20ccab3: Internal type cleanup of the encryption client (no runtime change). The exported operation classes EncryptOperation, EncryptQueryOperation, BatchEncryptQueryOperation and BulkEncryptOperation now declare that they accept a types.Json document as plaintext, which they always did at runtime; their getOperation() return types widen to match. The EncryptionClient interface changes only in what encrypt returns for a types.Json column; see the EncryptResult changeset.
• Updated dependencies [fb75f40]
• Updated dependencies [fd0ee91]
• Updated dependencies [f7f1c76]
  • @cipherstash/auth@1.0.0
  • @cipherstash/protect-ffi@0.33.1

@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 [0275684]
• Updated dependencies [c851db5]
• Updated dependencies [fd0ee91]
• Updated dependencies [bbb1bfa]
• Updated dependencies [20ccab3]
  • @cipherstash/eql@3.1.0
  • @cipherstash/stack@1.3.0

@cipherstash/eql@3.1.0

Minor Changes

• 0275684: The eql-bindings crate resolves an EQL type named as a string to its own Stack Encrypt plan (stack-encrypt feature). eql_bindings::encryption::targets carries a catalog-generated table of every EQL type a data plan may name as a field target — its name across languages, family and suffix, the plaintext ValueKind it takes, the indexes it carries, its query twin, and whether the engine can produce it today with the reason when not — and encrypt / decrypt / query entry points that dispatch on the name and run the type's derived EncryptFrom / DecryptInto, resolving to the EQL value's JSON bytes through the engine's Pending so a guest batches it with the rest of a plan. This is the EQL half of EQL types as plan field targets (Go and Rust plans cannot target EQL domains, so Go writes rows EQL cannot query — make domains plan field targets #1062): a Go data plan names TextEq and the guest returns the finished EQL value instead of assembling one. TextEq is the only producible type; every other name is refused with the plan's reason. The SQL surface and the TypeScript package are unchanged.
• 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

• 587d06e: The supply-chain skill names pip among the Dependabot ecosystems the repository monitors, and says that a pip requirements file installed in CI should pin every package with a hash and be installed with pip install --require-hashes --no-deps.

• bd7e55f: Fix invalid YAML in skills/stash-managed-platforms/SKILL.md frontmatter: the
  unquoted description contained a colon-space, so any YAML parser rejected the
  file (this broke cipherstash.com deploys, which mirror these skills at build
  time). Rewritten as a folded block scalar; the parsed description is
  byte-for-byte identical.

• e5a3575: The supply-chain skill names every Dependabot ecosystem the repository monitors, including the Go module and the Docker image the musl binaries are built in.

• fd0ee91: Document how OidcFederationStrategy serves many users through one client: the
  getJwt callback runs on every operation, in the caller's async context, and
  must return the JWT of the user behind the current request, and each user's
  JWT is exchanged for that user's own token (stack-auth's fix for
  stack-auth OidcFederationStrategy reuses one user's token for every user until it expires — lock context can bind to the wrong person #1045). One caveat is documented for the @cipherstash/stack
  client on the native entry, which calls the strategy from a background task so
  a request read from AsyncLocalStorage is not visible inside getJwt there
  yet: capture the request in the closure or build the client per request until
  @cipherstash/stack runs a second encryption engine (protect-ffi) — new major built on stack-encrypt (umbrella) #1065 lands. The docs and the stash-auth, stash-encryption,
  stash-supabase and stash-edge skills say so, and say that on earlier
  @cipherstash/auth releases a strategy caches one token for everyone, so a
  client there must serve one user.

• 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.

• bbb1bfa: encrypt on a types.Json column now types its result as Encrypted | null when the plaintext may be null. A null document has always resolved to { data: null } at runtime (it is stored as SQL NULL, not encrypted), but the result was typed Encrypted, so result.data.c compiled and then threw. encrypt is now generic over the plaintext's type: a literal null, or a value typed JsonDocument, gives data: Encrypted | null, through .withLockContext() and .audit() too. A value TypeScript knows is non-null, and every scalar column, still gives data: Encrypted. No runtime change. If your code reads result.data after encrypting a Json value that may be null, it must now check for null first. EncryptOperation and EncryptOperationWithLockContext take an optional result type parameter (default Encrypted), and the EncryptResult<P> helper type is exported from @cipherstash/stack/encryption.

  @cipherstash/stack-supabase: the per-term query-encryption fallback (used when the client has no bulkEncrypt) now rejects a null envelope instead of sending the string "null" as a filter operand, matching the bulk path.

  stash: the stash-encryption skill now says what encrypt returns for a null Json document.

• Updated dependencies [fb75f40]

• Updated dependencies [0275684]

• Updated dependencies [c851db5]

• Updated dependencies [fd0ee91]

• Updated dependencies [f7f1c76]

  • @cipherstash/auth@1.0.0
  • @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-drizzle@1.3.0

Patch Changes

• Updated dependencies [fd0ee91]
• Updated dependencies [bbb1bfa]
• Updated dependencies [20ccab3]
  • @cipherstash/stack@1.3.0

@cipherstash/stack-supabase@1.3.0

Patch Changes

• bbb1bfa: encrypt on a types.Json column now types its result as Encrypted | null when the plaintext may be null. A null document has always resolved to { data: null } at runtime (it is stored as SQL NULL, not encrypted), but the result was typed Encrypted, so result.data.c compiled and then threw. encrypt is now generic over the plaintext's type: a literal null, or a value typed JsonDocument, gives data: Encrypted | null, through .withLockContext() and .audit() too. A value TypeScript knows is non-null, and every scalar column, still gives data: Encrypted. No runtime change. If your code reads result.data after encrypting a Json value that may be null, it must now check for null first. EncryptOperation and EncryptOperationWithLockContext take an optional result type parameter (default Encrypted), and the EncryptResult<P> helper type is exported from @cipherstash/stack/encryption.

  @cipherstash/stack-supabase: the per-term query-encryption fallback (used when the client has no bulkEncrypt) now rejects a null envelope instead of sending the string "null" as a filter operand, matching the bulk path.

  stash: the stash-encryption skill now says what encrypt returns for a null Json document.

• Updated dependencies [fd0ee91]

• Updated dependencies [bbb1bfa]

• Updated dependencies [20ccab3]

  • @cipherstash/stack@1.3.0

@cipherstash/wizard@1.3.0

Patch Changes

• 472cbf0: Add @modelcontextprotocol/sdk ^1.32.0 as a direct dependency so the
  auto-installed peer of @anthropic-ai/claude-agent-sdk resolves to a release
  patched against GHSA-6qxp-vccf-f47h / CVE-2026-104850, instead of the vulnerable
  1.29.0 previously locked. The wizard never imports the MCP SDK directly — this
  is a peer-resolution pin only; no API change.
• Updated dependencies [fb75f40]
• Updated dependencies [fd0ee91]
  • @cipherstash/auth@1.0.0

@cipherstash/auth-darwin-arm64@1.0.0

@cipherstash/auth-darwin-x64@1.0.0

@cipherstash/auth-linux-arm64-gnu@1.0.0

@cipherstash/auth-linux-x64-gnu@1.0.0

@cipherstash/auth-linux-x64-musl@1.0.0

@cipherstash/auth-win32-x64-msvc@1.0.0

@cipherstash/e2e@0.0.8

Patch Changes

• Updated dependencies [587d06e]
• Updated dependencies [bd7e55f]
• Updated dependencies [e5a3575]
• Updated dependencies [fd0ee91]
• Updated dependencies [ae63dcd]
• Updated dependencies [bbb1bfa]
• Updated dependencies [20ccab3]
• Updated dependencies [472cbf0]
  • stash@1.3.0
  • @cipherstash/stack@1.3.0
  • @cipherstash/wizard@1.3.0

@cipherstash/basic-example@1.2.19

Patch Changes

• Updated dependencies [fd0ee91]
• Updated dependencies [bbb1bfa]
• Updated dependencies [20ccab3]
  • @cipherstash/stack@1.3.0
  • @cipherstash/stack-drizzle@1.3.0

@cipherstash/prisma-example@0.1.5

Patch Changes

• Updated dependencies [ae63dcd]
• Updated dependencies [fd0ee91]
• Updated dependencies [bbb1bfa]
• Updated dependencies [20ccab3]
  • @cipherstash/stack-prisma@1.3.0
  • @cipherstash/stack@1.3.0

@cipherstash/bench@0.0.10

Patch Changes

• Updated dependencies [fd0ee91]
• Updated dependencies [bbb1bfa]
• Updated dependencies [20ccab3]
  • @cipherstash/stack@1.3.0
  • @cipherstash/stack-drizzle@1.3.0

@cipherstash/ffi-integration-tests@1.0.3

Patch Changes

• Updated dependencies [fb75f40]
• Updated dependencies [fd0ee91]
• Updated dependencies [f7f1c76]
  • @cipherstash/auth@1.0.0
  • @cipherstash/protect-ffi@0.33.1

@cipherstash/test-kit@0.0.6

Patch Changes

• Updated dependencies [fd0ee91]
• Updated dependencies [bbb1bfa]
• Updated dependencies [20ccab3]
  • @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: 32f4d415-03f7-464d-8379-5884585f36bd

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

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

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

[freshtonic]

I did a second review of head 3edd56a67. I request changes for one reason: this release publishes @cipherstash/auth and its six platform packages as 1.0.0. No changeset asks for a major bump.

Blocking: @cipherstash/auth goes from 0.44.1 to 1.0.0

• The pending changesets give @cipherstash/auth one minor (oidc-federation-per-user-tokens.md) and one patch (auth-error-codes-and-help.md). The expected version is 0.45.0.
• The new languages/typescript/packages/auth/CHANGELOG.md entry is ## 1.0.0, but it has only "Minor Changes" and "Patch Changes".
• Cause: languages/typescript/packages/auth/package.json:80-87 lists the six platform packages as peerDependencies at workspace:*. The fixed group in .changeset/config.json gives the platforms the same minor bump. A minor bump of a peer that leaves the peer range makes changesets bump the dependent to major (@changesets/assemble-release-plan 6.0.10, dist/changesets-assemble-release-plan.cjs.js:340-343). workspace:* is an exact range, so every minor bump leaves it. The fixed group then moves all seven packages to 1.0.0.
• 0.44.1 was a patch release, so this did not occur before. All earlier minor releases were published from the old repository.
• protect-ffi does not have this problem. It lists its platforms as optionalDependencies (languages/typescript/packages/protect-ffi/package.json:105).
• A published 1.0.0 cannot be withdrawn. It tells users that the release has breaking changes, and it removes the 0.x line.

Fix options. Choose one before you merge:

1. Move the auth platforms to optionalDependencies, as protect-ffi does. Then let the bot regenerate this PR. Do a check that the native loader and auth-preflight.yml still pass.
2. Keep 1.0.0, but make the decision clear: add a major changeset for @cipherstash/auth that says why. Then the CHANGELOG has a "Major Changes" section that agrees with the version.

Also required before merge (not a code defect)

• No CI ran on this head. The only check is CodeRabbit. 40 workflow runs on changeset-release/main (Test EQL, Tests (Rust), Tests (Go), CodeQL, Require @cipherstash/auth changeset, and others) have the status action_required. Approve them, or push a commit that starts them, and get them green.
• Run the preflights. This release moves protect-ffi (0.33.0 to 0.33.1) and @cipherstash/auth. The last ffi-preflight.yml and auth-preflight.yml runs were on main (6 and 3 October). AGENTS.md says to dispatch them against the Version Packages branch before a release that moves these versions.

What I checked and found correct

• Version bumps agree with the 14 changesets. The fixed group moves stash, stack, stack-drizzle, stack-supabase, stack-prisma and wizard to 1.3.0 (stack minor). @cipherstash/eql 3.0.6 to 3.1.0 (two minors). protect-ffi 0.33.1. migrate 1.0.1. nextjs 4.4.1.
• EQL lockstep: the npm package, the eql-bindings crate, both release manifests, src/generated/release-manifest.ts and the COMMENT ON SCHEMA eql_v3 stamp in both bundles all say 3.1.0. The SQL diff changes only the stamp. eql-sql-asset-freshness.test.mjs passes (13 tests). eql-bindings requires stack-encrypt 0.2.0, which is on crates.io.
• sync-skill-pins.mjs moved the three pins in skills/stash-cli/SKILL.md:399 and skills/stash-edge/SKILL.md:79,94 to 1.3.0. No other exact pin is in skills/.
• node scripts/release-gate.mjs on this head exits 0, with ffi=true auth=true js=true.
• The scripts suite passes on this head. The only two failures came from stale local node_modules.

Suggested follow-up PR

• languages/typescript/packages/auth/README.md:94-95 gives a Deno import map with npm:@cipherstash/auth@^0.41/.... That range already excludes 0.44. It also excludes this release, so a reader who copies it does not get the per-user token fix for #1045. This README ships in the tarball.

[freshtonic]

Re-review of 6328f231e. The bot regenerated the PR on main (141054f5e). The new main commits are #1151 (sharp override, no changeset) and #1202 (EQL test fixtures, no changeset).

Delta

git range-diff 3edd56a67~1..3edd56a67 6328f231e~1..6328f231e reports the Version Packages commit as identical (=). The PR consumes the same 14 changesets. No new changeset merged, so no version changes.

Blocking: still open

• @cipherstash/auth and its six platform packages still go from 0.44.1 to 1.0.0. languages/typescript/packages/auth/package.json:80-87 still lists the platforms as peerDependencies at workspace:*. languages/typescript/packages/auth/CHANGELOG.md:3 is still ## 1.0.0 with only "Minor Changes" and "Patch Changes". The two fix options in my earlier review still apply.

Also required before merge: still open

• No CI ran on this head. The only check is CodeRabbit. The 19 workflow runs for 6328f231e all have the status action_required.
• Preflights not dispatched. The last ffi-preflight.yml run is on main at 5080d2d33 (6 October). The last auth-preflight.yml run is on main at 3e8f6cb8c (3 October). Neither ran on changeset-release/main.

Re-checked and still correct

Because the commit is identical, my earlier checks still apply: the other version bumps agree with the changesets, the EQL lockstep files all say 3.1.0, and the skill pins (skills/stash-cli/SKILL.md:399, skills/stash-edge/SKILL.md:79,94) say 1.3.0. #1151 and #1202 change no published package surface, so they correctly have no changeset.

Suggested follow-up PR

• Still open: languages/typescript/packages/auth/README.md:94-95 pins the Deno import map to ^0.41.