Python: Update chromadb requirement from >=0.5,<1.4 to >=0.5,<1.6 and fix azure-search-documents compatibility

[dependabot]

Motivation and Context

Updates the requirements on chromadb to permit the latest version (up to 1.6). Also fixes CI failures caused by azure-search-documents 11.7.0b2 removing internal _endpoint and _credential attributes from SearchIndexClient.

Description

Chromadb update:

• Updated chromadb requirement from >=0.5,<1.4 to >=0.5,<1.6 in pyproject.toml
• Updated uv.lock to resolve chromadb to version 1.5.9

Azure AI Search compatibility fix:

• Refactored _get_search_client in azure_ai_search.py to accept explicit endpoint and credential parameters instead of accessing removed private attributes (_endpoint, _credential) on SearchIndexClient
• Added _resolve_credential helper function to centralize credential resolution logic
• Added search_endpoint and search_credential fields to AzureAISearchCollection and AzureAISearchStore so endpoint/credential are stored and passed explicitly when creating SearchClient instances
• Updated unit tests to remove references to the removed private attributes, updated assertions, and added new tests for credential resolution and the pre-built client scenario

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

[github-actions]

Automated Code Review

Reviewers: 4 | Confidence: 93%

✓ Correctness

This is a simple upper-bound version bump for the chromadb dependency from < 1.4 to < 1.6. The change allows users to install newer chromadb versions. The existing code imports standard chromadb public APIs (Client, Collection, GetResult, QueryResult, ClientAPI, Settings, EmbeddingFunction, Space, and collection configuration classes) which are stable across minor versions. No correctness issues found.

✓ Security Reliability

This is a minimal, low-risk change that widens the upper version bound for the chromadb optional dependency from < 1.4 to < 1.6. There are no security or reliability concerns — it simply allows users to install newer chromadb versions (1.4.x and 1.5.x) which may contain their own bug fixes and security patches. No injection risks, secrets, resource leaks, or unsafe patterns are introduced.

✓ Test Coverage

This is a minor dependency upper-bound bump for chromadb from < 1.4 to < 1.6 in pyproject.toml. The existing unit tests in tests/unit/connectors/memory/test_chroma.py use MagicMock for the chromadb client, so they verify connector logic but don't exercise real chromadb API compatibility. No new behavior is introduced by relaxing a version constraint, so no new tests are strictly required. The existing test suite remains valid.

✗ Design Approach

I found one design-level issue: this PR widens the supported chromadb range to include 1.4/1.5 without any corresponding compatibility work or PR-time validation for the actual Chroma integration. That is risky here because the connector imports and calls Chroma-specific APIs directly, while the only pull-request coverage for Chroma is mocked unit tests; the real memory integration suite runs later in non-PR merge-gate/scheduled workflows.

Flagged Issues

• python/pyproject.toml:80 widens supported Chroma versions to <1.6, but the Chroma connector is tightly coupled to specific Chroma APIs (python/semantic_kernel/connectors/chroma.py:9-13, 123-180) and the PR path does not exercise a real Chroma client. Unit tests mock ClientAPI (python/tests/unit/connectors/memory/test_chroma.py:12-116), while the real memory integration suite only runs in non-PR jobs (.github/workflows/python-integration-tests.yml:299-355, 357-462). The better approach is to keep the existing cap until compatibility with 1.4/1.5 is explicitly verified, or add/update coverage that validates the connector against the newly admitted versions before widening the dependency range.

---

Automated review by dependabot[bot]'s agents

[github-actions]

This advertises support for Chroma 1.4/1.5, but the connector depends on Chroma-specific APIs (python/semantic_kernel/connectors/chroma.py:9-13, 123-180) and PR-time coverage does not exercise a real Chroma client: the unit tests mock ClientAPI (python/tests/unit/connectors/memory/test_chroma.py:12-116), while the real memory integration tests only run in non-PR jobs (.github/workflows/python-integration-tests.yml:299-355, 357-462). Please either keep the old cap until compatibility is verified, or add coverage that validates the connector against the newly admitted versions before widening the range.

[moonbox3]

@copilot: fix the CI/CD failures

[Copilot]

@copilot: fix the CI/CD failures

Fixed in commit Fix CI failures: update azure-search-documents compatibility and chromadb lock.

The CI failures were caused by azure-search-documents 11.7.0b2 removing the internal _endpoint and _credential attributes from SearchIndexClient. The fix:

1. Refactored _get_search_client to accept explicit endpoint and credential parameters instead of accessing private attributes on SearchIndexClient
2. Added a _resolve_credential helper function
3. Added search_endpoint and search_credential fields to AzureAISearchCollection and AzureAISearchStore
4. Updated tests to remove references to the removed private attributes and added new tests for the credential resolution logic
5. Updated uv.lock to reflect the chromadb >=0.5,<1.6 constraint (resolved to chromadb 1.5.9)

[moonbox3]

Superseded by #14176

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.