Skip to content

Releases

v0.33.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 19:49

[0.33.1] - 2026-11-08

Fixed

  • A function-grant reply whose registration map gives a pattern null rights
    ({"report_*": null}) is refused as a malformed response, as the Rust,
    Python, TypeScript and Kotlin clients refuse it. Previously the pattern was
    silently dropped. An explicit empty rights list still grants nothing.
  • The vendored test-fixtures/admin-function-permissions-contract.json is
    byte-identical to the shared contract again, including its accepted and
    refused reply shapes. A new test reads every shape on the key listing and on
    the modern and legacy aggregate permission reads.
  • Function grants read sorted by pattern in Unicode code-point order whichever
    shape the reply uses. A list reply used to keep the server's order while the
    registration map was sorted. The vendored fixture gains the shared contract's
    out-of-order list and a pattern pair whose code-point order differs from its
    UTF-16 order, in both shapes.

What's Changed

  • fix(admin): refuse null rights in a function-grant map reply, and read the shared reply shapes by @shyd0w in #116

Full Changelog: v0.33.0...v0.33.1

v0.33.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 20:03

[0.33.0] - 2026-11-07

Added

  • Stored-function call grants: CreateAPIKeyRequest.FunctionPermissions,
    FunctionPermissions on key records and the aggregate permission read, and
    List/Get/Put/DeleteAPIKeyFunctionPermissions addressed by key id.
    Patterns are validated before HTTP (non-empty, at most 256 bytes, no control
    or invisible character, * only last), and a server that predates the grants
    reads as none.
  • Bare . and .. patterns are rejected before sending: a bare dot segment
    cannot be addressed in a URL path, and the server refuses them as grant
    patterns too (since ekoDB 0.81.1).
  • UserFunction.RunAs (caller or author) and the read-only, server-recorded
    UserFunction.CreatedBy. Any other run_as value is refused both when a
    definition is decoded and before one is sent: SaveFunction,
    UpdateFunction, SaveUserFunction and UpdateUserFunction return an error
    without making a request, whichever body encoding the client uses.
  • Shared admin-function-permissions-contract.json fixture, vendored unchanged
    from the public client contract. Its rejected patterns include bare . and
    .., so the function-grant methods are tested against them directly.

What's Changed

  • feat(admin): stored-function call grants and function run_as/created_by by @shyd0w in #115

Full Changelog: v0.32.0...v0.33.0

v0.32.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 05:13

[0.32.0] - 2026-11-02

Added

  • Server-generated API-key IDs and key-addressed collection/KV permission reads,
    PUT, PATCH and DELETE. Typed before/after changes preserve field restrictions,
    unknown metadata and optional KV prefixes on facet responses.

Changed

  • Permission updates now take KeyID and return CollectionPermissionChange.
    Use the explicitly named legacy request and method for secret-valued 0.79.2
    updates. A cached authenticated route probe selects the generation, including
    prerelease servers whose version string still reports the older release.

Fixed

  • Generate UTC changelog headings and the suggested release-cap subject from
    make bump-version, with isolated regression checks for metadata generation,
    idempotence, invalid input, interactive input and EOF.
  • Match the explicit permission-facet Unicode contract using the shared name
    fixture, including accepted format characters and supplementary-plane names.
  • Reject malformed UTF-8 collection names and KV permission prefixes before
    capability probes or permission requests, while preserving valid Unicode
    replacement characters.
  • Retry failed legacy health reads without losing sanitized error details; cache
    only successfully read stable versions.
  • Restrict legacy capability fallback to direct permission-request 404/405
    responses, allowing failed token refreshes to propagate and recover.

What's Changed

  • feat(sdk): prepare permission resources and release tooling milestone by @shyd0w in #114

Full Changelog: v0.31.1...v0.32.0

v0.31.1

Choose a tag to compare

@github-actions github-actions released this 23 Oct 19:25

[0.31.1] - 2026-10-23

Security

  • Require patched Go 1.27.3. Raise the module's minimum toolchain version so
    local builds and the existing CI version-file selectors use the crypto/x509
    security patch for GO-2026-6809. Document rebuilding applications with the
    patched compiler. No public API or module dependency changes. (#107)

What's Changed

  • fix(security): require patched Go 1.27.3 by @shyd0w in #108

Full Changelog: v0.31.0...v0.31.1

v0.31.0

Choose a tag to compare

@github-actions github-actions released this 20 Oct 22:01

[0.31.0] - 2026-10-20

Added

  • Three-state field-restriction edits for admin permission updates: omitted
    pointers preserve, pointers to nil slices clear, and slices replace exactly.
    Gate updates on authenticated server 0.79.2 or later, retain unknown metadata
    including nested KV grants, and test the shared recorded contract plus
    concurrent version caching. Extend disposable live coverage and require the
    canonical five-SDK parity audit for Codex, Claude and Copilot. (#104)

  • Separate AdminClient for API-key creation, listing, revocation,
    current-token permissions and single-collection grant updates. Defaults to
    non-admin creation, preserves field restrictions on reads, redacts
    credential-bearing failures and avoids ambiguous create retries. Includes
    offline boundary tests and an opt-in disposable lifecycle test.
    Field-restriction writes require server support. (#102)

What's Changed

  • feat(admin): add a separate API-key management client by @shyd0w in #103

Full Changelog: v0.30.1...v0.31.0

v0.30.1

Choose a tag to compare

@github-actions github-actions released this 17 Oct 16:16

[0.30.1] - 2026-10-17

Changed

  • Align the Go module release version with the ekoDB client v0.30.1 release.
    There are no Go API or behavior changes.

What's Changed

  • chore: align Go client release at v0.30.1 by @shyd0w in #100

Full Changelog: v0.30.0...v0.30.1

v0.30.0

Choose a tag to compare

@github-actions github-actions released this 11 Oct 16:33

[0.30.0] - 2026-10-10

Added

  • Search execution path. SearchResponse.ExecutionPath preserves the
    server's optional vector-search execution_path, including future values.
    (#94)

Fixed

  • Go 1.27 lint compatibility. Pin golangci-lint v2.14.0 so local and CI lint
    can read Go 1.27.2 export data; v2.13.0 failed during typechecking.
  • Version bump regression coverage. An isolated fixture now checks valid,
    repeated, invalid, interactive, and EOF inputs without changing the repo's
    version file. (#87)

What's Changed

  • Milestone 0.30.0: Go client search response by @shyd0w in #95

Full Changelog: v0.29.0...v0.30.0

v0.29.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 17:13

[0.29.0] - 2026-10-08

Added

  • IndexConfig.Dimension and FieldTypeSchemaBuilder.Dimension set the
    optional vector length a vector index enforces from the first write. Unset
    values are omitted from JSON. (#92)

What's Changed

  • feat(schema): optional vector index dimension by @shyd0w in #93

Full Changelog: v0.28.0...v0.29.0

v0.28.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 13:38

[0.28.0] - 2026-10-08

Added

  • SearchQuery.EfSearch, SearchQueryBuilder.EfSearch, and optional
    vector-index efSearch expose HNSW query beam width in the search request and
    schema. Unset values are omitted from JSON. (#90)

Fixed

  • CI does no work on a draft PR and runs when the PR is marked ready. The
    pull_request trigger in unit-tests.yml now lists
    types: [opened, synchronize, reopened, ready_for_review], and the lint and
    go-tests jobs carry !github.event.pull_request.draft in their if:. The
    guard is a no-op on push runs. (#88)
  • Upsert now inserts with the requested ID on a miss and leaves the caller's
    map unchanged. The ID argument wins over a conflicting record["id"]; the
    operation remains a non-atomic read and write. (#90)

What's Changed

  • ci: do no work on draft PRs, run when a PR is marked ready by @shyd0w in #89
  • fix: preserve Upsert IDs and expose ef_search by @shyd0w in #91

Full Changelog: v0.27.0...v0.28.0

v0.27.0

Choose a tag to compare

@github-actions github-actions released this 16 Sep 22:16

[0.27.0] - 2026-09-16

Added

  • Function definitions now retain transaction_config, and modeled conditions
    preserve unknown fields while still providing typed access to known fields.
    (#65, #67, #76)
  • TriggerSchedule runs a schedule immediately through the schedule trigger
    endpoint. (#78)

Changed

  • StageEmbed now accepts the input and output field names required by the
    function API, StageBatchDelete sends record_ids, and
    StageHttpRequestWithOptions exposes the server's optional timeout and
    output-field controls without changing existing StageHttpRequest calls.
    (#79, #80)
  • BeginTransaction() can omit its isolation level to use the server default;
    existing calls that pass one isolation level remain source-compatible. (#81)
  • Schedule pause and resume operations now update the schedule's enabled state
    through the supported update endpoint. (#78)
  • KV document-link helpers now use the document-link routes, KVGetLinks
    returns the server's array response, and the link/unlink methods retain their
    existing two-result signatures. (#77)

Removed

  • ChatMessageRequest.ForceSummarize, which is silently ignored by the chat API
    and no longer has any effect. (#82, #84)

Fixed

  • Atomic update bodies now use lowercase field names in MessagePack mode, action
    sequences use their required JSON wire format, and collection restore reads
    the current cleared_count response field. RestoreRecordStatus exposes the
    server's restored boolean without breaking RestoreRecord.
  • README examples now use the current schedule-trigger, transaction-config,
    goal-status, and agent-model contracts.
  • make test now exits nonzero when the Go test command fails, and linked
    worktrees install hooks through Git's resolved hooks path while invalid hook
    state fails loudly. Hook fixtures also isolate nested Git commands from the
    repository running the hook. (#66)

Full Changelog: v0.26.4...v0.27.0