|
5 | 5 | from published versions since it shows up in the VS Code extension changelog |
6 | 6 | tab and is confusing to users. Add it back between releases if needed. --> |
7 | 7 |
|
| 8 | +## [v1.14.6](https://github.com/coder/vscode-coder/releases/tag/v1.14.6) 2026-05-26 |
| 9 | + |
| 10 | +### Changed |
| 11 | + |
| 12 | +- Minimum supported VS Code lowered to 1.105 for Cursor compatibility. |
| 13 | + |
| 14 | +### Removed |
| 15 | + |
| 16 | +- The "Coder Chat (Experimental)" secondary sidebar and its `agents` |
| 17 | + experiment gate. Deeplinks that still include `chatId` continue to open |
| 18 | + the workspace; the parameter is now silently ignored. |
| 19 | + |
| 20 | +### Fixed |
| 21 | + |
| 22 | +- Sessions suspended by an mTLS or `coder.headerCommand` failure now |
| 23 | + auto-recover once the setting is corrected; a 401 from a mid-flight |
| 24 | + settings change is retried silently with the new settings and fresh |
| 25 | + headers instead of escalating to an interactive prompt. |
| 26 | +- Logout, deployment switch, or dispose during an in-flight auth verify |
| 27 | + is no longer overwritten when the verify finishes, and no longer |
| 28 | + leaves stale deployment data in storage. |
| 29 | +- Cross-window login keeps listening when the first token observed from |
| 30 | + another window is invalid, so a follow-up valid write still resolves |
| 31 | + the dialog. |
| 32 | +- Config-change side-effects (reload prompt, recovery, reconnects) fire |
| 33 | + once after edits settle instead of on every event in a burst. |
| 34 | + |
| 35 | +### Security |
| 36 | + |
| 37 | +- Hardened the configuration scope of security-sensitive settings so that a |
| 38 | + malicious `.vscode/settings.json` cannot override them (SEC-200). Workspace |
| 39 | + and folder values are now ignored by VS Code for these settings. This closes |
| 40 | + a path where a workspace could redirect command execution |
| 41 | + (`coder.headerCommand`, `coder.tlsCertRefreshCommand`), substitute the CLI |
| 42 | + binary or its source (`coder.binarySource`, `coder.binaryDestination`, |
| 43 | + `coder.disableSignatureVerification`, `coder.enableDownloads`), inject |
| 44 | + CLI/SSH flags (`coder.globalFlags`, `coder.sshFlags`), swap TLS material or |
| 45 | + disable TLS verification (`coder.tlsCertFile`, `coder.tlsKeyFile`, |
| 46 | + `coder.tlsCaFile`, `coder.tlsAltHost`, `coder.insecure`), or override |
| 47 | + identity, networking, and credential storage (`coder.defaultUrl`, |
| 48 | + `coder.autologin`, `coder.useKeyring`, `coder.proxyBypass`, |
| 49 | + `coder.proxyLogDirectory`). |
| 50 | +- Path-, command-, and network-dependent settings use `"scope": "machine"` |
| 51 | + (per-machine, not synced via Settings Sync), while user-wide preferences |
| 52 | + (`coder.defaultUrl`, `coder.autologin`, `coder.useKeyring`, `coder.insecure`, |
| 53 | + `coder.disableSignatureVerification`, `coder.enableDownloads`) use |
| 54 | + `"scope": "application"`, which preserves Settings Sync across your |
| 55 | + machines while still blocking workspace overrides. This follows VS Code's |
| 56 | + [recommended scope semantics](https://code.visualstudio.com/api/references/contribution-points#contributes.configuration). |
| 57 | + |
8 | 58 | ## [v1.14.5](https://github.com/coder/vscode-coder/releases/tag/v1.14.5) 2026-04-30 |
9 | 59 |
|
10 | 60 | ### Added |
|
0 commit comments