|
42 | 42 | around `cmd.exe` on Windows) and a recurring command-injection risk |
43 | 43 | when deployment-supplied values like workspace names or template |
44 | 44 | parameters contained spaces, quotes, or shell metacharacters. |
45 | | -- Minimum supported VS Code lowered to 1.105 for Cursor compatibility. |
46 | | - |
47 | | -### Removed |
48 | | - |
49 | | -- The "Coder Chat (Experimental)" secondary sidebar and its `agents` |
50 | | - experiment gate. Deeplinks that still include `chatId` continue to open |
51 | | - the workspace; the parameter is now silently ignored. |
52 | 45 |
|
53 | 46 | ### Fixed |
54 | 47 |
|
|
72 | 65 | for input the update is failed instead of hanging, and the workspace |
73 | 66 | falls back to starting on the existing template version with a warning. |
74 | 67 |
|
| 68 | +## [v1.14.6](https://github.com/coder/vscode-coder/releases/tag/v1.14.6) 2026-05-26 |
| 69 | + |
| 70 | +### Changed |
| 71 | + |
| 72 | +- Minimum supported VS Code lowered to 1.105 for Cursor compatibility. |
| 73 | + |
| 74 | +### Removed |
| 75 | + |
| 76 | +- The "Coder Chat (Experimental)" secondary sidebar and its `agents` |
| 77 | + experiment gate. Deeplinks that still include `chatId` continue to open |
| 78 | + the workspace; the parameter is now silently ignored. |
| 79 | + |
| 80 | +### Fixed |
| 81 | + |
| 82 | +- Sessions suspended by an mTLS or `coder.headerCommand` failure now |
| 83 | + auto-recover once the setting is corrected; a 401 from a mid-flight |
| 84 | + settings change is retried silently with the new settings and fresh |
| 85 | + headers instead of escalating to an interactive prompt. |
| 86 | +- Logout, deployment switch, or dispose during an in-flight auth verify |
| 87 | + is no longer overwritten when the verify finishes, and no longer |
| 88 | + leaves stale deployment data in storage. |
| 89 | +- Cross-window login keeps listening when the first token observed from |
| 90 | + another window is invalid, so a follow-up valid write still resolves |
| 91 | + the dialog. |
| 92 | +- Config-change side-effects (reload prompt, recovery, reconnects) fire |
| 93 | + once after edits settle instead of on every event in a burst. |
| 94 | + |
75 | 95 | ### Security |
76 | 96 |
|
77 | 97 | - Hardened the configuration scope of security-sensitive settings so that a |
|
0 commit comments