Skip to content

RDBC-1168 RavenDB 27044 claude native - #609

Open
M4xymm wants to merge 1 commit into
ravendb:v7.2from
M4xymm:sdk-sync/RDBC-1168
Open

M4xymm wants to merge 1 commit into
ravendb:v7.2from
M4xymm:sdk-sync/RDBC-1168

Conversation

@M4xymm

@M4xymm M4xymm commented Oct 23, 2026

Copy link
Copy Markdown
Member

Issue link

https://issues.ravendb.net/issue/RDBC-1168

Description

AI connection strings can now use the native Anthropic (Claude) provider through AnthropicSettings.

Port of PR #23802

  • Changed: new AnthropicSettings (apiKey, model, endpoint, maxOutputTokens, reasoningEffort, enablePromptCache, apiVersion), AiConnectionString.anthropicSettings, "Anthropic" in AiConnectorType, enablePromptCache in IAiSettings.
  • Changed: AiConnectionString.validate() rejects Anthropic with the TextEmbeddings model type.
  • Not ported: the server chat completion client, the internal DefaultMaxOutputTokens and DefaultApiVersion constants (the server applies them), and the IAiSettings member on OllamaSettings (the Node.js OllamaSettings does not implement IAiSettings).
  • Tests: new unit tests in test/Documents/Operations/AI/AnthropicSettingsTest.ts for validation, endpoint resolution, compare and the connection string. The C# tests run against live LLM providers or test server internals and are not ported.
  • Checks: npm run prepare, lint, check-exports, check-imports and the new unit tests pass locally. No server tests were run locally.

Type of change

  • Bug fix
  • Regression bug fix
  • Optimization
  • New feature
  • Sync with the C# client (no version bump, versions are bumped at release)
  • Dependency / tooling / CI update

Target branch and backports

  • This PR targets the correct release branch (e.g. v7.2, v7.1, v7.0, v6.0)
  • The change needs to be ported to other release branches. Please list them.
  • No other release branch is affected

How risky is the change?

  • Low
  • Moderate
  • High
  • Not relevant

Backward compatibility

  • Non breaking change
  • Ensured. Please explain how has it been implemented?
  • Breaking change (public API, exported types, default behavior). Please describe the migration path.
  • Not relevant

Server compatibility

  • Works with all RavenDB server versions covered by CI
  • Requires a minimum server version. Please specify which one and make sure the tests are gated accordingly.
  • Not relevant

Affected runtimes

  • Node.js
  • Bun
  • Deno
  • Cloudflare Workers
  • Not runtime specific

Public API

  • New or changed public API. New types are exported from src/index.ts (npm run check-exports passes).
  • Version bump: package.json and CLIENT_VERSION in src/Http/RequestExecutor.ts (sync / release PRs only)
  • No public API changes

Documentation update

  • README.md has been updated
  • No documentation update is needed

Testing by Contributor

  • Tests have been added that prove the fix is effective or that the feature works
  • Existing tests verify the correct behavior
  • It has been verified by manual testing
  • npm run lint, npm run build, npm run check-exports and npm run check-imports pass locally
  • Tests have been run locally against a RavenDB server (RAVENDB_TEST_SERVER_PATH / RAVENDB_SERVER_VERSION)
  • Runtime-specific changes have been verified on the affected runtime (Bun / Deno / Cloudflare Workers)

Dependencies

  • New or updated runtime dependency. Please explain why it is needed and confirm it works on all affected runtimes.
  • Dev dependency only
  • No dependency changes

Is there any existing behavior change of other features due to this change?

  • Yes. Please list the affected features/subsystems and provide appropriate explanation
  • No

Ticket: RDBC-1168
C# change: ravendb/ravendb#23802

SDK Sync Agent

@M4xymm M4xymm added the sdk-sync Port of C# client changes from an SDK sync task label Oct 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sdk-sync Port of C# client changes from an SDK sync task

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant