Skip to content

release: v1.1.0 embedded#11

Merged
albedosehen merged 1 commit intomainfrom
release/1.1.0
Apr 13, 2026
Merged

release: v1.1.0 embedded#11
albedosehen merged 1 commit intomainfrom
release/1.1.0

Conversation

@albedosehen
Copy link
Copy Markdown
Collaborator

Merges the v1.1.0 embedded-connection commit back into main.

What's new

  • ConnectionConfig now accepts protocol: 'mem' | 'rocksdb' | 'surrealkv' | 'surrealkv+versioned' for in-process connections via @surrealdb/node / @surrealdb/wasm engine packages.
  • Persistent engines take an on-disk path; mem is ephemeral.
  • Credential-less embedded connections skip signin automatically.
  • Exported EMBEDDED_PROTOCOLS constant and isEmbeddedProtocol() type guard.
  • validateConnectionConfig() bypasses host/port/username/password checks for embedded.

Tests / quality

  • deno task test: 157 passed / 1607 steps
  • integration tests (auth + integration + integration_crud + integration_client): 6 passed / 173 steps
  • deno lint + deno fmt --check + deno check mod.ts all clean

Already published to JSR as @oneiriq/surql@1.1.0. npm publish still pending an NPM token refresh (non-blocking).

ConnectionConfig now accepts `protocol: 'mem' | 'rocksdb' | 'surrealkv' |
'surrealkv+versioned'` for in-process connections via the @surrealdb/node
(or @surrealdb/wasm) engine packages. Persistent engines take a `path`
field; `mem` is ephemeral. Credential-less embedded connections skip
signin automatically.

Exports `EMBEDDED_PROTOCOLS` + `isEmbeddedProtocol()` type guard.
`validateConnectionConfig()` bypasses host/port/username/password checks
when an embedded protocol is in use but still validates namespace and
database. Remote connections continue to work unchanged.

Enables edge/device deployments where each host owns its own SurrealDB
instance without a separate server process.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@albedosehen albedosehen merged commit 4322f5f into main Apr 13, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant