Conversation
|
|
||
| ## Version 1.31.0: February 19, 2026 | ||
| ### Enhancements | ||
| * Add support for `program` in attach debug configurations. [#14046](https://github.com/microsoft/vscode-cpptools/issues/14046) |
There was a problem hiding this comment.
This hasn't gone in yet. Maybe on Wednesday.
| ### Enhancements | ||
| * Add support for `program` in attach debug configurations. [#14046](https://github.com/microsoft/vscode-cpptools/issues/14046) | ||
| * Thanks for the contribution. [@Subham-KRLX (Subham)](https://github.com/Subham-KRLX) [PR #14108](https://github.com/microsoft/vscode-cpptools/pull/14108) | ||
| * Update SQLite to see if that fixes issues with the previous update. [#14142](https://github.com/microsoft/vscode-cpptools/issues/14142) |
There was a problem hiding this comment.
"previous update" is kind of vague and doesn't specify cpptools or sqlite being the issue. Maybe say "Update SQLite to check for fixes to issues introduced in version 3.50.4."
There was a problem hiding this comment.
I think I was intentionally vague. We reverted the change. I don't think users need to know which versions of SQLite are being switched to. "issues introduced in version 3.50.4" make it sound like those issues exist in 1.30.5, but we reverted the change, so I didn't want to go into all the messy details.
There was a problem hiding this comment.
i.e. the current text "previous update" is meant to refer to the previous update which got reverted. I wanted to keep the changelog entry simple. There are more details in the linked issue.
There was a problem hiding this comment.
Then maybe just say "Update SQLite to the latest version"
2 participants
No description provided.