mirror of
https://github.com/microsoft/semantic-kernel.git
synced 2026-10-12 02:19:06 +00:00
python-1.39.0
4823
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 Evan Mattson
|
9cb9aba41d |
Python: Bump to v1.39.0 for a release (#13392)
### Motivation and Context Bump to v1.39.0 for a release <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Description Bump to v1.39.0 for a release <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄dotnet-1.67.1-nightly-251125.1 python-1.39.0 |
||
|
Tao Chen
|
d84363f477 |
Python: Migrate to new Google GenAI SDK (#13371)
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Closes #12970, #13352 ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> 1. Migrate Google AI connector to use the new Google AI SDK. 2. This PR also marks the VertexAI connector as deprecated in favor of the Google AI connector. With this update, if users wants to connect to a VertexAI project instead of a Google AI endpoint, they can do so with the Google AI connector. 3. This PR also adds the ability for users to provide a custom client to the Google AI connector (#13352). 4. This PR also marks `AzureTextCompletion` deprecated. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄 |
||
|
Chris
|
5b30c8b703 |
.NET Fix - Surface agent failure for orchestration (#13369)
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Agent failure results in timeout for `OrchestrationResult`. Fixes: https://github.com/microsoft/semantic-kernel/issues/13149 Fixes: https://github.com/microsoft/semantic-kernel/issues/13040 Fixes: https://github.com/microsoft/semantic-kernel/issues/12987 ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> `AgentActor` exception being eaten by the agent-runtime and not exposed via the `TaskCompletionSource<>` used by the `OrchestrationResult`/ ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄dotnet-1.67.1-nightly-251122.1 |
||
|
SergeyMenshykh
|
73337db694 |
.Net: Enable argument types retention in handoff orchestration. (#13367)
This PR fixes the issue when an MCP function is called with an argument
that doesn't match the expected parameter type.
From chat:
```csharp
public async Task<string> GetDataAsync(
[Description("Optional modality type filter (CT, MRI, XA, etc.). Make sure it is a LIST of strings. Examples: ['CT'] or ['CT', 'MR']")] List<string>? modalityType = null,
(...............)
```
When we tested it using Semantic Kernel without MCP, it returned the
data in the correct format. However, when we integrated it into the tool
(one API Server where we initialize the Kernel and another MCP Server
with all the functions), we get the incorrect format:
<img width="1186" height="175" alt="image"
src="https://github.com/user-attachments/assets/9efd26e2-77fc-4ec2-85ed-60a35fa9e821"
/>
|
||
|
Adam SitnikandShay Rojansky
|
de20575aee |
Fixes to Get/Delete for Guid keys (#13353)
This PR fixes a bug reported offline by @jeffhandley
```log
fail: Microsoft.Extensions.DataIngestion.IngestionPipeline[6]
An error occurred while ingesting document 'Example_GPS_Watch.md'.
System.InvalidCastException: Unable to cast object of type 'System.Guid' to type 'System.String'.
at System.Linq.Enumerable.CastICollectionIterator`1.MoveNext()
at Azure.Search.Documents.Models.IndexDocumentsBatch.Delete(String keyName, IEnumerable`1 keyValues)
at Azure.Search.Documents.SearchClient.DeleteDocumentsAsync(String keyName, IEnumerable`1 keyValues, IndexDocumentsOptions options, CancellationToken cancellationToken)
at Microsoft.Extensions.VectorData.VectorStoreErrorHandler.RunOperationAsync[TResult,TException](VectorStoreCollectionMetadata metadata, String operationName, Func`1 operation)
at Microsoft.Extensions.DataIngestion.VectorStoreWriter`1.WriteAsync(IAsyncEnumerable`1 chunks, CancellationToken cancellationToken)
at Microsoft.Extensions.DataIngestion.IngestionPipeline`1.IngestAsync(IngestionDocument document, Activity parentActivity, CancellationToken cancellationToken)
at Microsoft.Extensions.DataIngestion.IngestionPipeline`1.ProcessAsync(IEnumerable`1 files, Activity rootActivity, CancellationToken cancellationToken)+MoveNext()
```
---------
Co-authored-by: Shay Rojansky <[email protected]>
dotnet-1.67.1-nightly-251114.1
dotnet-1.67.1-nightly-251113.1
|
||
|
Evan Mattson
|
849cff0b50 |
Python: Bump Python version to 1.38.0 for a release. (#13354)
### Motivation and Context Bump Python version to 1.38.0 for a release. <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Description Bump Python version to 1.38.0 for a release. <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄python-1.38.0 |
||
|
Nico MöllerandEvan Mattson
|
145ad9bfd2 |
Python: Upgrade Onnx Connector to use 0.9.0 (#13162)
### Motivation and Context Fixes : #13001 ### Description Package version 0.9.0 introduced very helpful methods like applying chat templates automatically from the tokenizer and also support for multi audio & image files. This PR adds the following functionalities: - [x] Add Inference with multiple Images - [x] Add Inference with multiple Audios - [x] Chat Templates for non Multimodal Models are read via onnx ### Samples Text Sample with ONNX: <img width="1728" height="90" alt="image" src="https://github.com/user-attachments/assets/b93d9fc1-4e38-4fa9-b535-cc316e0900ed" /> Image Sample with ONNX : <img width="1721" height="91" alt="image" src="https://github.com/user-attachments/assets/47761beb-b728-4936-a6b6-fd253e041689" /> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄 --------- Co-authored-by: Evan Mattson <[email protected]> |
||
|
westeyandCopilot
|
b1ecee2d0e |
.Net: Add OpenAPI tool call migration sample for AzureOpenAI (#13339)
### Motivation and Context Moving sample from AF to SK repos to avoid circular package reference. ### Description - Add OpenAPI tool call migration sample to AF migration samples which can be linked from the AF repo. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄 --------- Co-authored-by: Copilot <[email protected]>dotnet-1.67.1-nightly-251110.1 |
||
|
Dmytro Struk
|
1ccdd1e649 | .Net: Updated package version (#13342) dotnet-1.67.1-nightly-251109.1 dotnet-1.67.1-nightly-251108.1 dotnet-1.67.1-nightly-251107.1 dotnet-1.67.1 | ||
|
Shay Rojansky
|
eab8c88983 |
.Net: [MEVD] Fix Guid (and other) keys for dynamic collections (#13341)
Closes #13340 |
||
|
Shay Rojansky
|
a5810db1df |
.Net: Final test cleanup (#13328)
I think this completes the cleanup work I had planned on the tests.dotnet-1.67.0-nightly-251106.1 |
||
|
Tao Chen
|
b2cceb5985 |
.Net: Update OTel GenAI operation names (#13334)
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> OTel GenAI operation names have the following updates: 1. `chat.completion` to `chat` 2. `text.completion` to `text_completion` ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> This PR updates those operation names ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄dotnet-1.67.0-nightly-251105.1 dotnet-1.67.0-nightly-251104.1 |
||
|
westey
|
2464458c47 |
.Net: Update SK Version for release (#13327)
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄dotnet-1.67.0-nightly-251103.1 dotnet-1.67.0 |
||
|
icycaandRoger Barreto
|
13e7582856 |
.Net: Fix #13232: Add empty parameters schema for NonInvocableTool placeholder (#13278)
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> 1. Why is this change required? NonInvocableTool placeholder is created without a parameters field, which causes 422 errors when used with Mistral models via LiteLLM since Mistral enforces stricter JSON schema validation than other AI providers. 2. What problem does it solve? Current Issue: When Semantic Kernel has no invocable tools but needs to send tools to keep the service happy, it includes the NonInvocableTool placeholder. This lacks a parameters field, causing Mistral APIs to reject requests. 3. What scenario does it contribute to? This fix enables SK to work with: - Mistral cloud APIs - Any AI provider with strict schema validation requirements Use Cases: Applications using Mistral as their AI provider Enterprise applications with strict API validation requirements 4. Fixes: #13232 ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Solution Updated the NonInvocableTool creation to include a proper empty parameters schema that satisfies Mistral's validation requirements while maintaining backward compatibility with all other providers Changes Made File: src/Connectors/Connectors.OpenAI/Core/ClientCore.ChatCompletion.cs Line 61-64: Enhanced s_nonInvocableFunctionTool with proper parameters schema Added: Comprehensive unit tests verifying schema structure and Mistral compatibility Existing Tests: All 474 OpenAI connector tests pass (1 skipped) Integration Tests: Verified with local Mistral via Ollama + LiteLLM Backward Compatibility: Confirmed no breaking changes with OpenAI and other providers Note: I 've noticed that this similar empty schema is used as a property called `s_zeroFunctionParametersSchema` that exists at `OpenAIFunction.cs` ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄 Co-authored-by: Roger Barreto <[email protected]> |
||
|
Federico LauriantiandDmytro Struk
|
70b7bdb62b |
.Net: KernelProcessEventData deserialized in LocalAgentStep (#13203)
### Motivation and Context 1. **Why is this change required?** Because `LocalAgentStep` was passing `KernelProcessEventData` wrappers directly into `KernelArguments`, unlike `LocalStep` which unwraps them. This inconsistency caused agents to receive JSON-like data instead of the actual payload. 2. **What problem does it solve?** It ensures that agents receive the real value (e.g. the user’s message text) instead of the wrapper object, preventing confusing model responses like *“you seem to be passing a json”*. 3. **What scenario does it contribute to?** Agent-based process pipelines (for example a simple chat process where user input is sent to an agent). The agent now correctly sees the user input as plain text or object, improving reliability and user experience. ### Description This PR updates `LocalAgentStep` so that it unwraps `KernelProcessEventData` before passing it into `KernelArguments["message"]`. * If `TargetEventData` is a `KernelProcessEventData`, we now call `.ToObject()` to get the real value. * If it is not, we keep the value as it is. * This makes `LocalAgentStep` consistent with `LocalStep.AssignStepFunctionParameterValues`. With this change, agents no longer receive the wrapper object but the actual payload (for example the plain user input), which avoids the model interpreting it as JSON. ### Contribution Checklist - [X] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass - [X] I didn't break anyone 😄 Co-authored-by: Dmytro Struk <[email protected]> |
||
|
Shay Rojansky
|
3eb869e1e8 |
.Net: [MEVD] More test cleanup (#13320)
Another batch of test cleanup work - this almost concludes what I have planned for the tests. * We no longer create any collections with GUID names; all collections have a manually-defined name, and are deleted when a test starts running. This ensures that no collections are left behind if a test crashes or is stopped in the middle, and makes it easier to examine the database. * Removed global SimpleRecord and SimpleFixture, each test suite now has its own record and fixture. * Cleaned up and renamed DistanceFunctionTests to only focus on testing the different distance functions, and added corresponding tests elsewhere. * Added IndexKindTests to specifically cover different index types. |
||
|
dependabot[bot]
|
802efdc56a |
.Net: Bump axios from 1.9.0 to 1.12.0 in /dotnet/samples/Demos/ProcessFrameworkWithSignalR (#13119)
Bumps [axios](https://github.com/axios/axios) from 1.9.0 to 1.12.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/axios/axios/releases">axios's releases</a>.</em></p> <blockquote> <h2>Release v1.12.0</h2> <h2>Release notes:</h2> <h3>Bug Fixes</h3> <ul> <li>adding build artifacts (<a href="https://github.com/axios/axios/commit/9ec86de257bfa33856571036279169f385ed92bd">9ec86de</a>)</li> <li>dont add dist on release (<a href="https://github.com/axios/axios/commit/a2edc3606a4f775d868a67bb3461ff18ce7ecd11">a2edc36</a>)</li> <li><strong>fetch-adapter:</strong> set correct Content-Type for Node FormData (<a href="https://redirect.github.com/axios/axios/issues/6998">#6998</a>) (<a href="https://github.com/axios/axios/commit/a9f47afbf3224d2ca987dbd8188789c7ea853c5d">a9f47af</a>)</li> <li><strong>node:</strong> enforce maxContentLength for data: URLs (<a href="https://redirect.github.com/axios/axios/issues/7011">#7011</a>) (<a href="https://github.com/axios/axios/commit/945435fc51467303768202250debb8d4ae892593">945435f</a>)</li> <li>package exports (<a href="https://redirect.github.com/axios/axios/issues/5627">#5627</a>) (<a href="https://github.com/axios/axios/commit/aa78ac23fc9036163308c0f6bd2bb885e7af3f36">aa78ac2</a>)</li> <li><strong>params:</strong> removing '[' and ']' from URL encode exclude characters (<a href="https://redirect.github.com/axios/axios/issues/3316">#3316</a>) (<a href="https://redirect.github.com/axios/axios/issues/5715">#5715</a>) (<a href="https://github.com/axios/axios/commit/6d84189349c43b1dcdd977b522610660cc4c7042">6d84189</a>)</li> <li>release pr run (<a href="https://github.com/axios/axios/commit/fd7f404488b2c4f238c2fbe635b58026a634bfd2">fd7f404</a>)</li> <li><strong>types:</strong> change the type guard on isCancel (<a href="https://redirect.github.com/axios/axios/issues/5595">#5595</a>) (<a href="https://github.com/axios/axios/commit/0dbb7fd4f61dc568498cd13a681fa7f907d6ec7e">0dbb7fd</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>adapter:</strong> surface low‑level network error details; attach original error via cause (<a href="https://redirect.github.com/axios/axios/issues/6982">#6982</a>) (<a href="https://github.com/axios/axios/commit/78b290c57c978ed2ab420b90d97350231c9e5d74">78b290c</a>)</li> <li><strong>fetch:</strong> add fetch, Request, Response env config variables for the adapter; (<a href="https://redirect.github.com/axios/axios/issues/7003">#7003</a>) (<a href="https://github.com/axios/axios/commit/c959ff29013a3bc90cde3ac7ea2d9a3f9c08974b">c959ff2</a>)</li> <li>support reviver on JSON.parse (<a href="https://redirect.github.com/axios/axios/issues/5926">#5926</a>) (<a href="https://github.com/axios/axios/commit/2a9763426e43d996fd60d01afe63fa6e1f5b4fca">2a97634</a>), closes <a href="https://redirect.github.com/axios/axios/issues/5924">#5924</a></li> <li><strong>types:</strong> extend AxiosResponse interface to include custom headers type (<a href="https://redirect.github.com/axios/axios/issues/6782">#6782</a>) (<a href="https://github.com/axios/axios/commit/7960d34eded2de66ffd30b4687f8da0e46c4903e">7960d34</a>)</li> </ul> <h3>Contributors to this release</h3> <ul> <li><!-- raw HTML omitted --> <a href="https://github.com/WillianAgostini" title="+132/-16760 ([#7002](https://github.com/axios/axios/issues/7002) [#5926](https://github.com/axios/axios/issues/5926) [#6782](https://github.com/axios/axios/issues/6782) )">Willian Agostini</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/DigitalBrainJS" title="+4263/-293 ([#7006](https://github.com/axios/axios/issues/7006) [#7003](https://github.com/axios/axios/issues/7003) )">Dmitriy Mozgovoy</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/mkhani01" title="+111/-15 ([#6982](https://github.com/axios/axios/issues/6982) )">khani</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/AmeerAssadi" title="+123/-0 ([#7011](https://github.com/axios/axios/issues/7011) )">Ameer Assadi</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/emiedonmokumo" title="+55/-35 ([#6998](https://github.com/axios/axios/issues/6998) )">Emiedonmokumo Dick-Boro</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/opsysdebug" title="+8/-8 ([#6980](https://github.com/axios/axios/issues/6980) )">Zeroday BYTE</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/jasonsaayman" title="+7/-7 ([#6985](https://github.com/axios/axios/issues/6985) [#6985](https://github.com/axios/axios/issues/6985) )">Jason Saayman</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/HealGaren" title="+5/-7 ([#5715](https://github.com/axios/axios/issues/5715) )">최예찬</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/gligorkot" title="+3/-1 ([#5627](https://github.com/axios/axios/issues/5627) )">Gligor Kotushevski</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/adimit" title="+2/-1 ([#5595](https://github.com/axios/axios/issues/5595) )">Aleksandar Dimitrov</a></li> </ul> <h2>Release v1.11.0</h2> <h2>Release notes:</h2> <h3>Bug Fixes</h3> <ul> <li>form-data npm pakcage (<a href="https://redirect.github.com/axios/axios/issues/6970">#6970</a>) (<a href="https://github.com/axios/axios/commit/e72c193722530db538b19e5ddaaa4544d226b253">e72c193</a>)</li> <li>prevent RangeError when using large Buffers (<a href="https://redirect.github.com/axios/axios/issues/6961">#6961</a>) (<a href="https://github.com/axios/axios/commit/a2214ca1bc60540baf2c80573cea3a0ff91ba9d1">a2214ca</a>)</li> <li><strong>types:</strong> resolve type discrepancies between ESM and CJS TypeScript declaration files (<a href="https://redirect.github.com/axios/axios/issues/6956">#6956</a>) (<a href="https://github.com/axios/axios/commit/8517aa16f8d082fc1d5309c642220fa736159110">8517aa1</a>)</li> </ul> <h3>Contributors to this release</h3> <ul> <li><!-- raw HTML omitted --> <a href="https://github.com/izzygld" title="+186/-93 ([#6970](https://github.com/axios/axios/issues/6970) )">izzy goldman</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/manishsahanidev" title="+70/-0 ([#6961](https://github.com/axios/axios/issues/6961) )">Manish Sahani</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/noritaka1166" title="+12/-10 ([#6938](https://github.com/axios/axios/issues/6938) [#6939](https://github.com/axios/axios/issues/6939) )">Noritaka Kobayashi</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/jrnail23" title="+13/-2 ([#6956](https://github.com/axios/axios/issues/6956) )">James Nail</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/Tejaswi1305" title="+1/-1 ([#6894](https://github.com/axios/axios/issues/6894) )">Tejaswi1305</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/axios/axios/blob/v1.x/CHANGELOG.md">axios's changelog</a>.</em></p> <blockquote> <h1><a href="https://github.com/axios/axios/compare/v1.11.0...v1.12.0">1.12.0</a> (2025-09-11)</h1> <h3>Bug Fixes</h3> <ul> <li>adding build artifacts (<a href="https://github.com/axios/axios/commit/9ec86de257bfa33856571036279169f385ed92bd">9ec86de</a>)</li> <li>dont add dist on release (<a href="https://github.com/axios/axios/commit/a2edc3606a4f775d868a67bb3461ff18ce7ecd11">a2edc36</a>)</li> <li><strong>fetch-adapter:</strong> set correct Content-Type for Node FormData (<a href="https://redirect.github.com/axios/axios/issues/6998">#6998</a>) (<a href="https://github.com/axios/axios/commit/a9f47afbf3224d2ca987dbd8188789c7ea853c5d">a9f47af</a>)</li> <li><strong>node:</strong> enforce maxContentLength for data: URLs (<a href="https://redirect.github.com/axios/axios/issues/7011">#7011</a>) (<a href="https://github.com/axios/axios/commit/945435fc51467303768202250debb8d4ae892593">945435f</a>)</li> <li>package exports (<a href="https://redirect.github.com/axios/axios/issues/5627">#5627</a>) (<a href="https://github.com/axios/axios/commit/aa78ac23fc9036163308c0f6bd2bb885e7af3f36">aa78ac2</a>)</li> <li><strong>params:</strong> removing '[' and ']' from URL encode exclude characters (<a href="https://redirect.github.com/axios/axios/issues/3316">#3316</a>) (<a href="https://redirect.github.com/axios/axios/issues/5715">#5715</a>) (<a href="https://github.com/axios/axios/commit/6d84189349c43b1dcdd977b522610660cc4c7042">6d84189</a>)</li> <li>release pr run (<a href="https://github.com/axios/axios/commit/fd7f404488b2c4f238c2fbe635b58026a634bfd2">fd7f404</a>)</li> <li><strong>types:</strong> change the type guard on isCancel (<a href="https://redirect.github.com/axios/axios/issues/5595">#5595</a>) (<a href="https://github.com/axios/axios/commit/0dbb7fd4f61dc568498cd13a681fa7f907d6ec7e">0dbb7fd</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>adapter:</strong> surface low‑level network error details; attach original error via cause (<a href="https://redirect.github.com/axios/axios/issues/6982">#6982</a>) (<a href="https://github.com/axios/axios/commit/78b290c57c978ed2ab420b90d97350231c9e5d74">78b290c</a>)</li> <li><strong>fetch:</strong> add fetch, Request, Response env config variables for the adapter; (<a href="https://redirect.github.com/axios/axios/issues/7003">#7003</a>) (<a href="https://github.com/axios/axios/commit/c959ff29013a3bc90cde3ac7ea2d9a3f9c08974b">c959ff2</a>)</li> <li>support reviver on JSON.parse (<a href="https://redirect.github.com/axios/axios/issues/5926">#5926</a>) (<a href="https://github.com/axios/axios/commit/2a9763426e43d996fd60d01afe63fa6e1f5b4fca">2a97634</a>), closes <a href="https://redirect.github.com/axios/axios/issues/5924">#5924</a></li> <li><strong>types:</strong> extend AxiosResponse interface to include custom headers type (<a href="https://redirect.github.com/axios/axios/issues/6782">#6782</a>) (<a href="https://github.com/axios/axios/commit/7960d34eded2de66ffd30b4687f8da0e46c4903e">7960d34</a>)</li> </ul> <h3>Contributors to this release</h3> <ul> <li><!-- raw HTML omitted --> <a href="https://github.com/WillianAgostini" title="+132/-16760 ([#7002](https://github.com/axios/axios/issues/7002) [#5926](https://github.com/axios/axios/issues/5926) [#6782](https://github.com/axios/axios/issues/6782) )">Willian Agostini</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/DigitalBrainJS" title="+4263/-293 ([#7006](https://github.com/axios/axios/issues/7006) [#7003](https://github.com/axios/axios/issues/7003) )">Dmitriy Mozgovoy</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/mkhani01" title="+111/-15 ([#6982](https://github.com/axios/axios/issues/6982) )">khani</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/AmeerAssadi" title="+123/-0 ([#7011](https://github.com/axios/axios/issues/7011) )">Ameer Assadi</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/emiedonmokumo" title="+55/-35 ([#6998](https://github.com/axios/axios/issues/6998) )">Emiedonmokumo Dick-Boro</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/opsysdebug" title="+8/-8 ([#6980](https://github.com/axios/axios/issues/6980) )">Zeroday BYTE</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/jasonsaayman" title="+7/-7 ([#6985](https://github.com/axios/axios/issues/6985) [#6985](https://github.com/axios/axios/issues/6985) )">Jason Saayman</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/HealGaren" title="+5/-7 ([#5715](https://github.com/axios/axios/issues/5715) )">최예찬</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/gligorkot" title="+3/-1 ([#5627](https://github.com/axios/axios/issues/5627) )">Gligor Kotushevski</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/adimit" title="+2/-1 ([#5595](https://github.com/axios/axios/issues/5595) )">Aleksandar Dimitrov</a></li> </ul> <h1><a href="https://github.com/axios/axios/compare/v1.10.0...v1.11.0">1.11.0</a> (2025-07-22)</h1> <h3>Bug Fixes</h3> <ul> <li>form-data npm pakcage (<a href="https://redirect.github.com/axios/axios/issues/6970">#6970</a>) (<a href="https://github.com/axios/axios/commit/e72c193722530db538b19e5ddaaa4544d226b253">e72c193</a>)</li> <li>prevent RangeError when using large Buffers (<a href="https://redirect.github.com/axios/axios/issues/6961">#6961</a>) (<a href="https://github.com/axios/axios/commit/a2214ca1bc60540baf2c80573cea3a0ff91ba9d1">a2214ca</a>)</li> <li><strong>types:</strong> resolve type discrepancies between ESM and CJS TypeScript declaration files (<a href="https://redirect.github.com/axios/axios/issues/6956">#6956</a>) (<a href="https://github.com/axios/axios/commit/8517aa16f8d082fc1d5309c642220fa736159110">8517aa1</a>)</li> </ul> <h3>Contributors to this release</h3> <ul> <li><!-- raw HTML omitted --> <a href="https://github.com/izzygld" title="+186/-93 ([#6970](https://github.com/axios/axios/issues/6970) )">izzy goldman</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/manishsahanidev" title="+70/-0 ([#6961](https://github.com/axios/axios/issues/6961) )">Manish Sahani</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/noritaka1166" title="+12/-10 ([#6938](https://github.com/axios/axios/issues/6938) [#6939](https://github.com/axios/axios/issues/6939) )">Noritaka Kobayashi</a></li> <li><!-- raw HTML omitted --> <a href="https://github.com/jrnail23" title="+13/-2 ([#6956](https://github.com/axios/axios/issues/6956) )">James Nail</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/axios/axios/commit/0d8ad6e1de0f5339e02bc262d6f0df4936974120"><code>0d8ad6e</code></a> chore(release): v1.12.0 (<a href="https://redirect.github.com/axios/axios/issues/7013">#7013</a>)</li> <li><a href="https://github.com/axios/axios/commit/fd7f404488b2c4f238c2fbe635b58026a634bfd2"><code>fd7f404</code></a> fix: release pr run</li> <li><a href="https://github.com/axios/axios/commit/a2edc3606a4f775d868a67bb3461ff18ce7ecd11"><code>a2edc36</code></a> fix: dont add dist on release</li> <li><a href="https://github.com/axios/axios/commit/9ec86de257bfa33856571036279169f385ed92bd"><code>9ec86de</code></a> fix: adding build artifacts</li> <li><a href="https://github.com/axios/axios/commit/945435fc51467303768202250debb8d4ae892593"><code>945435f</code></a> fix(node): enforce maxContentLength for data: URLs (<a href="https://redirect.github.com/axios/axios/issues/7011">#7011</a>)</li> <li><a href="https://github.com/axios/axios/commit/28e5e3016d6ed0b3ec489427e4ec00133f45ddc2"><code>28e5e30</code></a> chore(sponsor): update sponsor block (<a href="https://redirect.github.com/axios/axios/issues/7005">#7005</a>)</li> <li><a href="https://github.com/axios/axios/commit/d03f245a40ec016b190748a865cce9fe3815c903"><code>d03f245</code></a> chore(CI): fixed release info script to use npm registry instead of git as fi...</li> <li><a href="https://github.com/axios/axios/commit/a0bc91137950f36a1f6b0a2a60d11fd7f245ff0e"><code>a0bc911</code></a> chore: removing dist files from src (<a href="https://redirect.github.com/axios/axios/issues/7002">#7002</a>)</li> <li><a href="https://github.com/axios/axios/commit/c959ff29013a3bc90cde3ac7ea2d9a3f9c08974b"><code>c959ff2</code></a> feat(fetch): add fetch, Request, Response env config variables for the adapte...</li> <li><a href="https://github.com/axios/axios/commit/a9f47afbf3224d2ca987dbd8188789c7ea853c5d"><code>a9f47af</code></a> fix(fetch-adapter): set correct Content-Type for Node FormData (<a href="https://redirect.github.com/axios/axios/issues/6998">#6998</a>)</li> <li>Additional commits viewable in <a href="https://github.com/axios/axios/compare/v1.9.0...v1.12.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/microsoft/semantic-kernel/network/alerts). </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
Andrea Sciutto
|
6ce98f76ef |
.Net: fix: AutorRole.Developer missing (#13310)
1. Why is this change required? AuthorRole.Developer was missing from the ModelDiagnostic.RoleToEventMap configuration. This was causing OpenTelemetry diagnostic to throw exceptions when the Developer role was used 2. What problem does it solve? Fixes the dictionary so exception are no longer occurring 3. What scenario does it contribute to? Enabling open telemetry and using developer messages 4. If it fixes an open issue, please link to the issue here. https://github.com/microsoft/semantic-kernel/issues/13302 |
||
|
westey
|
fbdbaab89e |
.Net: Fix top/skip bug in Azure AI Search (#13326)
### Motivation and Context #13324 ### Description - Fix top/skip bug in Azure AI Search ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄 |
||
|
|
c804629012 |
.Net: Add Gemini usage metadata CachedContentTokenCount and ThoughtsTokenC… (#13208)
Add missing usage variables in GeminiMetadata class ### Motivation and Context Gemini gives us CachedContentTokenCount and ThoughtsTokenCount to know how much of cost have the request. The total input as Gemini eyes is not only PromptTokenCount, but a sum of these 3 variables. ### Description Added CachedContentTokenCount and ThoughtsTokenCount variables, filled by the response and add test. **As I am beginner in C#, I can build and pass the test, also I can make an .nupkg of the code changed, but I can't test on other projects, so PLEASE check that before submitting changes. Thank you so much** ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X ] The code builds clean without any errors or warnings - [X ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X ] All unit tests pass, and I have added new tests where possible - [ X] I didn't break anyone 😄 --------- Co-authored-by: Rodrigo <[email protected]> Co-authored-by: Mark Wallace <[email protected]> Co-authored-by: Roger Barreto <[email protected]> |
||
|
Shay Rojanskyandwestey
|
d595e48e14 |
.Net: [MEVD] Fix dynamic batching APIs for PostgreSQL (#13323)
Fixes #13303 --------- Co-authored-by: westey <[email protected]> |
||
|
Shay Rojansky
|
ad97c3a654 |
.Net: [MEVD] Support BinaryEmbedding with PostgreSQL (#13322)
The main motivation here was to ensure that our infrastructure and tests properly support binary embeddings (and more in general, non-float/half ones). Closes #13321 |
||
|
MillmerandSergeyMenshykh
|
b03c3d030c |
.Net: Support Support BinaryContent in Gemini Connector (#13140)
### Motivation and Context Resolves: #13131 ### Description The Gemini connector actually already supports arbitrary base64 PDF content by prioritising binary data in the `CreateGeminiPartFromImage` function in the `GeminiRequest.cs`. I kept the current behaviour with the `ImageContent` and `AudioContent` but also added explicit support for the `BinaryContent` KernelContent type in the `GetGeminiPartFromKernelContent` function to bring it inline with how the other connectors work. I applied the same Chat Completion Unit test as those I found in the OpenAI Connector for BinaryContent. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone (I think...) 😄 --------- Co-authored-by: SergeyMenshykh <[email protected]> |
||
|
dependabot[bot]
|
1fc6a630d3 |
.Net: Bump vite from 6.2.7 to 6.4.1 in /dotnet/samples/Demos/ProcessWithCloudEvents/ProcessWithCloudEvents.Client (#13274)
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.2.7 to 6.4.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vitejs/vite/releases">vite's releases</a>.</em></p> <blockquote> <h2>[email protected]</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/[email protected]/packages/create-vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.4.1</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.4.1/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>[email protected]</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/[email protected]/packages/create-vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.4.0</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.4.0/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.7</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.7/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.6</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.6/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.5</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.5/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.4</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.4/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.3</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.3/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.2</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.2/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>[email protected]</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/[email protected]/packages/create-vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.1</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.1/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>[email protected]</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/[email protected]/packages/create-vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.0</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.0/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.0-beta.2</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.0-beta.2/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.0-beta.1</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.0-beta.1/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> <h2>v6.3.0-beta.0</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v6.3.0-beta.0/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vitejs/vite/commit/a7349ef31e3c2d7d9889ca629d43935745b7044e"><code>a7349ef</code></a> release: v6.3.1</li> <li><a href="https://github.com/vitejs/vite/commit/a152b7cbac72e05668f8fc23074d531ecebb77a5"><code>a152b7c</code></a> fix: backward compat for internal plugin <code>transform</code> calls (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19878">#19878</a>)</li> <li><a href="https://github.com/vitejs/vite/commit/35c7f35e2b67f2158ededf2af58ecec53b3f16c5"><code>35c7f35</code></a> fix: avoid using <code>Promise.allSettled</code> in preload function (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19805">#19805</a>)</li> <li><a href="https://github.com/vitejs/vite/commit/5fdcfe77a93ca7bc90a5427a2a20eceaee1c4da1"><code>5fdcfe7</code></a> release: v6.3.0</li> <li><a href="https://github.com/vitejs/vite/commit/d4ee5e8655a85f4d6bebc695b063d69406ab53ac"><code>d4ee5e8</code></a> fix(hmr): avoid infinite loop happening with <code>hot.invalidate</code> in circular dep...</li> <li><a href="https://github.com/vitejs/vite/commit/50034340401b4043bb0b158f18ffb7ae1b7f5c86"><code>5003434</code></a> fix(preview): use host url to open browser (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19836">#19836</a>)</li> <li><a href="https://github.com/vitejs/vite/commit/bf9728e79e8df905de457e15001e65e33cf13f0e"><code>bf9728e</code></a> release: v6.3.0-beta.2</li> <li><a href="https://github.com/vitejs/vite/commit/380c10e665e78ef732a8d7b6c8f60a1226fc4c3b"><code>380c10e</code></a> fix(hmr): run HMR handler sequentially (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19793">#19793</a>)</li> <li><a href="https://github.com/vitejs/vite/commit/8bed1de5710f2a097af0e22a196545446d98f988"><code>8bed1de</code></a> fix: addWatchFile doesn't work if base is specified (fixes <a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19792">#19792</a>) (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19794">#19794</a>)</li> <li><a href="https://github.com/vitejs/vite/commit/0a0c50a7ed38017469ed6dcec941c2d8d0efd0d0"><code>0a0c50a</code></a> refactor: simplify pluginFilter implementation (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/19828">#19828</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vitejs/vite/commits/[email protected]/packages/vite">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/microsoft/semantic-kernel/network/alerts). </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
Shay Rojansky
|
a39b2ba476 |
.Net: [MEVD] Conformance tests for multi-vector records (#13319)
Closes #11709 |
||
|
Shay Rojansky
|
b697358398 |
.Net: [MEVD] Go over all key types, add support for Guid (#13315)
* Added new KeyTypeTests to cover provider key support, alongside the existing DataTypeTests and EmbeddingTypeTests; moved all three into TypeTests folder. * As discussed offline, this adds Guid-as-string key support for all providers. From research this seems to be very standard practice across a wide range of databases: JSON-based databases generally encode various types (e.g. DateTime) as string, and Guids are standard there. Sqlite is similar, with Microsoft.Data.Sqlite supporting it natively. This notably allows upper layers to assume that they can always use Guid, which helps MEDI ([see this issue](https://github.com/dotnet/extensions/issues/6973)). * Per-provider notes * Azure AI Search: string only supported, added Guid-as-string as an option ([docs](https://learn.microsoft.com/en-us/rest/api/searchservice/data-type-map-for-indexers-in-azure-search#bkmk_sql_search) encouraging mapping Guid to strings) * MongoDB/CosmosMongoDB: Added int and long support (Guid was already supported). * CosmosNoSql: Added Guid-as-string (standard practice) * Pinecone: Added Guid-as-string * Redis: Added Guid-as-string * SQL Server: removed DateTime and `byte[]` as key types (as above) and added Guid. * SQLite: The Microsoft.Data.Sqlite (the low-level ADO.NET provider we're built on top of) supports GUIDs as TEXT; so it's really not us deciding to support - it's the lower-level driver. In addition, we support mapping boolean to INTEGER (1/0), which seems similar. Added support as data property as well, not just key. Closes #11784 Closes #12182dotnet-1.66.0-nightly-251102.2 dotnet-1.66.0-nightly-251101.1 |
||
|
Chris
|
d9ea1e396d |
.Net - Performance Fix for Orchestration Result (#13317)
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Using synchronous `WaitAll` creates extra CPU load at scale. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Use asynchronous `WhenAny` with timeout for modern .NET and using `Delay` task for .netstandard. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄dotnet-1.66.0-nightly-251031.1 |
||
|
Eduard van Valkenburg
|
1c11258a32 |
Python: added af_tool bridge for kernel_functions (#13227)
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Adds a new method to KernelFunction that creates a Agent Framework Tool from that function. Does require the user to install agent-framework-core themselves. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄 |
||
|
Evan Mattson
|
265130743d |
Python: Bump Python version to 1.37.1 for a release. (#13314)
### Motivation and Context Bump Python version to 1.37.1 for a release. <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Description Bump Python version to 1.37.1 for a release. <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄dotnet-1.66.0-nightly-251030.1 python-1.37.1 |
||
|
|
9962d434ab |
Python: Fixed sending "text" parameter to OpenAI Responses API (#13280)
## Summary
Fixed an issue where the `text` parameter was missing in requests to the
OpenAI Responses API.
## Changes Made
Modified the `ResponsesAgentThreadActions._generate_options()` method to
correctly handle the `text` parameter:
- Added to the options dictionary **only** if `text` is not `None`.
- Not added if it is an empty dict (the default value).
- This ensures that **only explicitly set `text` parameters** are sent
to the API.
## Fix Location
**File:**
`semantic_kernel/agents/open_ai/responses_agent_thread_actions.py`
**Before:**
```python
options = {
"model": merged.get("model"),
"top_p": merged.get("top_p"),
"temperature": merged.get("temperature"),
"truncation": truncation,
"metadata": merged.get("metadata"),
"max_output_tokens": max_output_tokens,
"parallel_tool_calls": parallel_tool_calls,
}
```
**After:**
```python
options = {
"model": merged.get("model"),
"top_p": merged.get("top_p"),
"temperature": merged.get("temperature"),
"truncation": truncation,
"metadata": merged.get("metadata"),
"max_output_tokens": max_output_tokens,
"parallel_tool_calls": parallel_tool_calls,
}
# Add text option if it exists
if merged.get("text") is not None:
options["text"] = merged.get("text")
```
- Closes #13281
### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
---------
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Evan Mattson <[email protected]>
|
||
|
Evan Mattson
|
05d659d6e9 |
Python: Fix non-string KernelArguments being converted to strings in prompt template function calls (#13292)
### Motivation and Context Fixes #13199 - Non-string kernel arguments are now preserved when passed to functions in prompt templates. Adds unit tests. <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [X] I didn't break anyone 😄 |
||
|
|
1f8fea2b49 |
Python: Fix ai connector integration tests (#13311)
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Vertex AI and Bedrock integration tests have been failing. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> 1. This PR fixes the vertex ai integration tests by upgrading the Google AI SDK version. 2. This PR fixes the Bedrock integration tests by upgrading the models. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄 --------- Co-authored-by: Copilot <[email protected]> Co-authored-by: moonbox3 <[email protected]> |
||
|
Evan Mattson
|
f5fb44e02a |
Python: Bump weaviate image to 1.33.3 (#13313)
### Motivation and Context Weaviate server needs a bump. <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [X] The code builds clean without any errors or warnings - [X] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [X] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄 |
||
|
Shay Rojansky
|
cc43169f44 |
.Net: [MEVD] Test cleanup pack (#13307)
This is an (almost) entirely test-only cleanup (I plan to do a bit more
later).
* Remove BasicQueryTests, rename BasicFilterTests to FilterTests and
move out to the root
* BasicFilterTests and BasicQueryTests both run the same filter
scenarios, the former via SearchAsync and the latter via filtering
GetAsync. Although in theory, some filter query construct could work in
one but not in the other, in practice no such example exists in the 12
providers we have (all databases use the same filter language/engine for
both APIs. So we had needless duplication for all the various test
exceptions/customizations, which had to be overridden in exactly the
same way in both test suites.
* At least for now, decided to remove BasicQueryTests as it adds
maintenance burden without any real coverage; coverage (included missing
coverage) specifically for filtered GetAsync was added separately (e.g.
we weren't testing ordering, skip/take with filtered get).
* If we do want to add back support for all query constructs (I'd want
to have a good reason to do so), I'd do that within FilterTests: just
like each scenario already exercises both static and dynamic models, it
could run GetAsync as well.
* Renamed CollectionConformanceTests to CollecitonManagementTests and
moved it out to the root.
* In general, this PR removes "Conformance" from the test type names.
* Big cleanup/refactor of all the so-called CRUD tests.
* We now have a ModelTests folder with a test suite for each different
model; BasicModelTests covers Get/Upsert/Delete (and their batching
variants) for the basic scenario (strongly-typed model with data
properties and a single vector property). Alongside that we have
DynamicModelTests, NoDataModelTests, NoVectorModelTests (I'll be added
MultipleVectorsModelTests).
* These tests no longer use random GUIDs for the collection name
(difficult to debug, the collection never gets cleaned up if the test
crashes/is stopped in the middle), but rather has fixed names per test
suite.
* The collection is created once per test suite, but cleared and
reseeded between each test run, providing full isolation (previously we
had no isolation, and documented each record in the seed data as
belonging to this scenario or that - which is brittle).
* Many other small improvements and cleanup.
Part of #12507
|
||
|
Shay Rojansky
|
c79c269794 |
.Net: [MEVD] Fix filtering by true (#13294)
Fixes #13293dotnet-1.66.0-nightly-251029.1 |
||
|
James AbbottandRoger Barreto
|
96c470185d |
.Net: Feature/gemini function parts format (#13258)
### Motivation and Context
1. Why is this change required?
It appears that there's a quirk to how Gemini handles tool call results
in it's API. The tool responses need to be present in the same chat item
as the tool requests - rather than adding them individually as separate
chat history items.
2. What problem does it solve?
This _appears_ to fix (at least in my use case) the error whereby you
receive:
```
{
"error": {
"code": 400,
"message": "Please ensure that the number of function response parts is equal to the number of function call parts of the function call turn.",
"status": "INVALID_ARGUMENT"
}
}
```
4. Which appears to happen when an SK response auto invokes > 1 tool.
When it's a single tool result the API appears to handle the response
gracefully.
5. https://github.com/microsoft/semantic-kernel/issues/12823
6. https://github.com/microsoft/semantic-kernel/issues/12528
-->
### Description
Google Gemini expects the function responses to be grouped together in a
single message rather than split across multiple separate messages with
role "function". By adding a batch tool result overload to the
GeminiChatMessage we can correctly parse the multiple parts of the
function call into their respective function parts.
### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
FYI @stephentoub (As I see you're working in the Gemini connector
recently)
---------
Co-authored-by: Roger Barreto <[email protected]>
|
||
|
|
3434190968 |
.Net: Fix #13183: .NET — Kernel.AddOpenAIChatClient throws an error when us… (#13198)
### Motivation and Context
1. Why is this change required?
When using AddOpenAIChatClient with a custom endpoint parameter but
without providing a custom httpClient, the code would create an
HttpClient without setting its BaseAddress property. This mismatch
between the HttpClient configuration and the
OpenAIClientOptions.Endpoint setting causes SSL/TLS handshake failures.
2. What problem does it solve?
This PR fixes the SSL connection error
(System.ClientModel.ClientResultException: The SSL connection could not
be established) that occurs when users call:
```
var kernel = Kernel.CreateBuilder()
.AddOpenAIChatClient(
modelId: "model-name",
apiKey: "api-key",
endpoint: new Uri("https://custom-endpoint.com")
)
.Build();
```
3. What scenario does it contribute to?
This enables users to easily connect to OpenAI-compatible endpoints
(such as Azure OpenAI, local LLM servers, or other OpenAI-compatible
APIs) without having to manually create and configure an HttpClient
instance.
Fixes SSL connection failures when using custom endpoints with the
default HttpClient.
4. Related Issue:
https://github.com/microsoft/semantic-kernel/issues/13183
### Description
Changes made:
Fixed invalid GetOpenAIClientOptions call in the first overload (lines
40-77):
Removed the unused GetOpenAIClientOptions call at lines 56-59
Added missing endpoint and orgId parameters to the
GetOpenAIClientOptions call used in OpenAIClient construction
Fixed SSL issue in the third overload with custom endpoint (lines
125-170):
Added logic to ensure the HttpClient has the correct BaseAddress when
using a custom endpoint
When no custom httpClient is provided and the default client has no
BaseAddress, creates a new HttpClient with BaseAddress set to the
provided endpoint
This ensures consistency between the HttpClient.BaseAddress and
OpenAIClientOptions.Endpoint, preventing SSL certificate validation
failures
Verified AddOpenAIEmbeddingGenerator methods:
Confirmed both overloads are correctly implemented with no similar
issues
The root cause was that HttpClientPipelineTransport uses the HttpClient
for making requests, but when the HttpClient.BaseAddress is null and the
endpoint is only set in OpenAIClientOptions.Endpoint, the SSL/TLS
handshake fails due to hostname mismatch during certificate validation.
The fix ensures that when a custom endpoint is provided, the HttpClient
is properly configured with the matching BaseAddress, allowing SSL/TLS
to validate the certificate correctly.
### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [V ] The code builds clean without any errors or warnings
- [ V] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [V ] All unit tests pass, and I have added new tests where possible
- [V ] I didn't break anyone 😄
---------
Co-authored-by: Roger Barreto <[email protected]>
Co-authored-by: westey <[email protected]>
|
||
|
Evan Mattson
|
cf9a5f21f7 |
Python: Fix onnx pkg by pinning. Pin openai < 2.0. (#13284)
### Motivation and Context For the latest onnxruntime 1.23.2 pkg: our GitHub Actions run is failing because uv is not matching the macOS wheel tag. Pinning to last-known-good until it's sorted out. - Pin openai pkg < 2.0 until we can investigate if 2.0 brings in other breaking changes. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄dotnet-1.66.0-nightly-251028.1 dotnet-1.66.0-nightly-251027.1 dotnet-1.66.0-nightly-251026.1 dotnet-1.66.0-nightly-251025.1 dotnet-1.66.0-nightly-251024.1 |
||
|
Shay Rojansky
|
3bc2a64fca |
.Net: [MEVD] [SQL Server] Support DateTimeOffset and string arrays (#13269)
Closes #13268 /cc @yorek @uc-msft (this uses JSON and JSON_CONTAINS() to map `string[]` to the database and perform Contains over them. |
||
|
Shay Rojansky
|
7fbe0374b3 |
.Net: [MEVD] [SQLServer] Switch from JSON to the new binary SqlVector (#13266)
Update SqlClient to 6.1.2 and use the new `SqlVector<float>` type, which allows efficient binary encoding of vector data (rather than the previous JSON-basd transfer). Closes #12220 /cc @yorek |
||
|
Shay Rojansky
|
1761c6864e |
.Net: [MEVD] Support MemoryExtensions.Contains in LINQ filters (#13263)
This makes the provider filters compatible with C# 14 (see #12504, and https://github.com/dotnet/runtime/issues/109757 on the runtime side). Note that this changes the entire repo to build with dotnet SDK 10.0 (rc2) - that's probably a good idea regardless to test with the latest, ensure compatibility etc. (but if this is problematic, let me know - it's only truly necessary for test coverage and can be reverted). I'm not happy to have the implementation duplicated across the implementations: we have FilterTranslationPreprocessor for common LINQ filter preprocessing, and that would be the ideal place for this. However, rewriting MemoryExtensions.Contains to Enumerable.Contains would require doing MethodInfo.MakeGenericMethod which is incompatible with NativeAOT. I considered have a fake, non-invocable MethodInfo implementation to represent the closed generic MethodInfo to Enumerable.Contains (MethodInfo and Type are abstract, so we can create custom implementations compatible with NativeAOT), but that's quite involved/complicated. The better story here is probably to have a base class implementation for the provider filter processors, which recognizes specific patterns and dispatches to abstract handlers which specific implementations override; it would take care of recognizing the various Contains variants. Note also that we already have duplication around Enumerable.Contains and List.Contains (the instance method), so this just adds another variant (for now). I'll think about cleaning this up. Fixes #12504 |
||
|
Tao Chen
|
5fec3bee83 |
.Net: Add Kernel Function Arguments and Result to execute tool span (#13241)
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> SK .Net is missing two attributes to the `execute_tool` span: `gen_ai.tool.call.arguments` and `gen_ai.tool.call.result`. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Add those two attributes to the span if sensitive data is turned on. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄dotnet-1.66.0-nightly-251023.1 |
||
|
Stephen Toub
|
caa6e1167f | .Net: Update ModelContextProtocol to 0.4.0-preview.3 (#13271) dotnet-1.66.0-nightly-251022.1 | ||
|
|
2530daf727 |
.Net: Add .NET VoiceChat console demo: Microphone → VAD → STT → Chat → TTS → Speaker (#12992)
### Motivation and Context Resolves microsoft/semantic-kernel#12916 While the repo already includes an `OpenAIRealtime` demo, this sample shows how **Semantic Kernel** can power a classic, production-style voice pipeline: **VAD → STT → Chat (SK) → TTS → Speaker** This is an end-to-end console app that: - **Uses voice activity detection (VAD)** to skip silence, reducing unnecessary API calls and latency. - **Uses TPL Dataflow** for structured, asynchronous message passing and backpressure, making the flow easier to extend or integrate. - **Streams responses end-to-end**, so the user hears audio as the LLM generates text. - **Runs entirely in a console**, no additional UI frameworks required. This makes the sample representative of real-world voice-agent architecture while remaining minimal and easy to run. Please note that demo is x64 due Web RTC VAD (WebRtcVadSharp) package. --------- Co-authored-by: Andrew Syrov <[email protected]> Co-authored-by: Roger Barreto <[email protected]> |
||
|
westeyandRoger Barreto
|
fb29385cb9 |
.Net: Bugfixes for SemanticKernelAIAgent (#13252)
### Motivation and Context #13254 ### Description - Fix two bugs related to duplicate text output, one for final text and the other for function results. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄 --------- Co-authored-by: Roger Barreto <[email protected]>dotnet-1.66.0-nightly-251021.1 |
||
|
Stephen Toub
|
4c030fef51 | .Net: Update to M.E.AI 9.10 (#13248) dotnet-1.66.0-nightly-251020.1 dotnet-1.66.0-nightly-251019.1 | ||
|
Roger Barreto
|
0ae3794ae8 |
.Net: Add Agent Framework Migration Samples (#13251)
### Motivation and Context Bring SK Migration Agent Framework samples into Semantic Kernel repo.dotnet-1.66.0-nightly-251016.1 |
||
|
westey
|
c989c5aeb3 |
.Net: Add adapters to allow SK agents to be exposed as AIAgent (#13240)
### Motivation and Context https://github.com/microsoft/agent-framework/issues/1122 ### Description Add adapters to allow SK agents to be exposed as AIAgent ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄dotnet-1.66.0-nightly-251015.1 |
||
|
Stratosandwestey
|
3ac786164d |
.Net: Fix weaviate collection name checking (#13242)
### Motivation and Context According to the weaviate document, the collection name allows the use of underscores - [collections](https://docs.weaviate.io/weaviate/config-refs/collections#class): `The collection name validation regex is /^[A-Z][_0-9A-Za-z]*$/.` ### Description Allow `_` in weaviate collection name. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄 --------- Co-authored-by: westey <[email protected]>dotnet-1.66.0-nightly-251014.1 |
||
|
westey
|
1526dbc736 |
.Net: Support CollectionExistsAsync with redis alpine (#13244)
### Motivation and Context #12734 Redis alpine produces a different error message for not found indices to redis stack. ### Description - Support CollectionExistsAsync with redis alpine ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄 |