From 7b960d9325273798a59b3d37bf54a344904be491 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Sun, 20 Sep 2026 12:53:20 +0000 Subject: [PATCH 1/3] chore(deps): bump tauri-plugin-shell Bumps the cargo group with 1 update in the /desktop/src-tauri directory: [tauri-plugin-shell](https://github.com/tauri-apps/plugins-workspace). Updates `tauri-plugin-shell` from 2.2.0 to 2.2.1 - [Release notes](https://github.com/tauri-apps/plugins-workspace/releases) - [Commits](https://github.com/tauri-apps/plugins-workspace/compare/os-v2.2.0...os-v2.2.1) --- updated-dependencies: - dependency-name: tauri-plugin-shell dependency-version: 2.2.1 dependency-type: direct:production dependency-group: cargo ... Signed-off-by: dependabot[bot] --- desktop/src-tauri/Cargo.lock | 4 ++-- desktop/src-tauri/Cargo.toml | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/desktop/src-tauri/Cargo.lock b/desktop/src-tauri/Cargo.lock index 95bc1a674a6..03fbb85ca93 100644 --- a/desktop/src-tauri/Cargo.lock +++ b/desktop/src-tauri/Cargo.lock @@ -3968,9 +3968,9 @@ dependencies = [ [[package]] name = "tauri-plugin-shell" -version = "2.2.0" +version = "2.2.1" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "bb2c50a63e60fb8925956cc5b7569f4b750ac197a4d39f13b8dd46ea8e2bad79" +checksum = "69d5eb3368b959937ad2aeaf6ef9a8f5d11e01ffe03629d3530707bbcb27ff5d" dependencies = [ "encoding_rs", "log", diff --git a/desktop/src-tauri/Cargo.toml b/desktop/src-tauri/Cargo.toml index 8683695613f..390da66bc36 100644 --- a/desktop/src-tauri/Cargo.toml +++ b/desktop/src-tauri/Cargo.toml @@ -23,7 +23,7 @@ tauri = { version = "=2.11.6", features = ["tray-icon", "image-png"] } tauri-plugin-autostart = "=2.5.0" tauri-plugin-opener = "=2.5.3" tauri-plugin-process = "=2.3.0" -tauri-plugin-shell = "=2.2.0" +tauri-plugin-shell = "=2.2.1" tauri-plugin-single-instance = "=2.4.0" tauri-plugin-updater = "=2.9.0" tokio = { version = "=1.45.1", features = ["sync", "time"] } From e230b3c0a6e9d02ddc56fb8ef63e0ac0ce238863 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Sun, 20 Sep 2026 13:14:23 +0000 Subject: [PATCH 2/3] test(openai-chat): declare the developer-role destination in the dangling tool_calls suite #5334 made foldDeveloperRoleToSystem tri-state: absent folds the developer role to system on the wire, false records a destination known to accept it. The other ordering suites were updated to declare their destination; this one was missed, so its barrier-placement assertions read role "system" where they expect "developer". These cases are about where the barrier lands relative to repaired tool calls, not which role carries it, so declare foldDeveloperRoleToSystem: false on the shared provider fixture. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- tests/adapters/openai/openai-chat-dangling-toolcalls.test.ts | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tests/adapters/openai/openai-chat-dangling-toolcalls.test.ts b/tests/adapters/openai/openai-chat-dangling-toolcalls.test.ts index 41a61c21023..9dabd359b4d 100644 --- a/tests/adapters/openai/openai-chat-dangling-toolcalls.test.ts +++ b/tests/adapters/openai/openai-chat-dangling-toolcalls.test.ts @@ -12,6 +12,10 @@ const provider: OcxProviderConfig = { baseUrl: "https://example.test/v1", apiKey: "sk-test", authMode: "key", + // These cases assert where a barrier lands relative to repaired tool calls, not which role + // carries it. The wire role folds to `system` unless a destination is recorded as accepting + // `developer`, so the destination is declared here to keep the assertions on their own role. + foldDeveloperRoleToSystem: false, }; interface ChatMsg { From 245f64a1e676f763041d1abd7a9827061c8d9ccd Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Sun, 20 Sep 2026 13:25:37 +0000 Subject: [PATCH 3/3] test(responses): declare the developer-role destination in the inline-document suite #5334 made foldDeveloperRoleToSystem tri-state: absent folds the developer role to system on the wire, false records a destination known to accept it. The inline-document bytes suite was missed, so its 'keeps its role' assertion read role "system" where it expects "developer". These cases are about the document reaching the wire intact, not which role carries it, so declare foldDeveloperRoleToSystem: false on the shared provider fixture. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- tests/responses/chat-inline-document-bytes.test.ts | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tests/responses/chat-inline-document-bytes.test.ts b/tests/responses/chat-inline-document-bytes.test.ts index dd88fa05788..1d9c7c75b1d 100644 --- a/tests/responses/chat-inline-document-bytes.test.ts +++ b/tests/responses/chat-inline-document-bytes.test.ts @@ -28,6 +28,10 @@ const chatProvider: OcxProviderConfig = { adapter: "openai-chat", baseUrl: "https://gateway.example.internal/v1", apiKey: "k", + // The wire role folds to `system` unless the destination is recorded as accepting + // `developer`; these cases assert the document survives the trip, so the destination is + // declared here to keep the developer-turn assertion reading its own role. + foldDeveloperRoleToSystem: false, }; const anthropicProvider = { adapter: "anthropic",