Skip to content

chore(deps, cpp): update ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer-metadata.json - #97

Open
embedded-releaser-app[bot] wants to merge 1 commit into
mainfrom
feature/embedded-devcontainer-cpp/update-vscode-extensions-devcontainer-metadata.json
Open

chore(deps, cpp): update ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer-metadata.json#97
embedded-releaser-app[bot] wants to merge 1 commit into
mainfrom
feature/embedded-devcontainer-cpp/update-vscode-extensions-devcontainer-metadata.json

Conversation

@embedded-releaser-app

@embedded-releaser-app embedded-releaser-app Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Note

Before merging this PR, please conduct a manual test checking basic functionality of the updated plug-ins. There are limited automated tests for the VS Code Extension updates.

Updates sonarsource.sonarlint-vscode from 5.6.0 to 5.8.1

Release notes

For full release notes, see JIRA

For full release notes, see JIRA

For full release notes, see JIRA

Updates ms-vscode.cpptools from 1.32.2 to 1.33.8

Release notes

Instructions

The extension can be obtained by one of the methods below:

  • Install the "C/C++" or "C/C++ Extension Pack" extension published by Microsoft from the Extensions view in VS Code.
  • Download a vsix that matches your OS from the Assets section below (and install it via the method mentioned above). The previous download methods have the vsix signatures verified by the Marketplace, but for this method, you can do the verification by downloading the matching manifest and signature.p7s file and running npx [at]vscode/vsce@latest verify-signature -i <.vsix> -m <.signature.manifest> -s <.signature.p7s> vscode-vsce#1044.

Requirements

  • VS Code 1.77.0 or later (March 2023).
  • Windows 10+ (x64, arm64), macOS 10.13+, Linux (Ubuntu 16+, etc.).
    • Debugging is not supported on CentOS 7 or RHEL 7. The last supported version was 1.22.11: #13219.
    • The last supported version for Windows 7 and 8 was 1.30.5.

Changes

New Feature

  • Unification of tag parsing with the VS implementation. In particular, it's now done using multiple parallel cpptools-srv2 processes. PR #14426

Enhancements

  • Allow platform overrides in cppbuild tasks. #11601
  • Add the debuginfod launch option to the cppdbg debugger schema. #14458, #14460, PR #14471, PR #14506, MIEngine#1562
  • Add the ignoreRunWithoutDebuggingWarnings property to allow 'Run without debugging' warnings to be suppressed. #14515

Bug Fixes

  • Fix the wording for the #include errors detected message. #8227
  • Fix an incorrect invalid type conversion IntelliSense error. #11294
  • Fix include completion (with recursive includes) still suggesting headers from a deleted folder. #12636
  • Fix a spurious recursive includes (**) debug console log warning for paths merged from c_cpp_properties.json when C_Cpp.mergeConfigurations is enabled. #14125
  • Fix 'Find All References' dropping valid references when a template parameter type has a typedef alias in only one translation unit. #14344
  • Fix the remote process picker ps command not working with some shells. #14442
  • Fix a spurious IntelliSense error with class template argument deduction (CTAD). #14453, #14459, #14504
  • Add important to C_Cpp.doxygen.sectionTags. PR #14473
  • Update the minimum supported VS Code version to 1.77. PR #14502
  • Fix issues with the debugger launch.json schema. PR #14523
  • Fix [[no_unique_address]] empty-base layout sizeof being computed too large. #14524
  • Fix ${env:VAR} and ${env.VAR} not expanding to an empty string when the environment variable is unset, to match VS Code's behavior. PR #14535
  • Fix C/C++ debug data-tips on members of a dereferenced expression. PR #14540
    • Thanks for the contribution. @tieo
  • Fix Windows backslash paths being mangled when adding an SSH target. PR #14554
  • Fix 'Run C/C++ File' not running the program in PowerShell when terminal shell integration is unavailable. #14583
  • Fix the build tools walkthrough for Visual Studio 2026. PR #14589
  • Fix custom configurations being discarded when C_Cpp.mergeConfigurations is enabled and a provider supplies the file uri as a vscode.Uri. #14621
  • Fix a tag parser crash when a UTF-8 string literal is concatenated with a narrow string literal containing an invalid multibyte sequence.
  • Fix IntelliSense incorrectly resolving #include files through a symbolic link after the target directory was deleted from disk.
  • Fix potential browse database corruption when the same workspace is opened by multiple processes on Linux and macOS.
  • Fix crashes when reading files saved in certain multibyte encodings such as GB18030 or EUC-JP.
  • Fix empty database folders being created in every folder of a multi-root workspace.
  • Fix the C_Cpp.refactoring.includeHeader setting not honoring always.
  • Fix spurious IntelliSense error on std::variant brace-initialization.
  • Fix several potential deadlocks and data races in the language server.
  • Fix an incorrect file path in an error message on Windows.
  • Reduce memory usage to help avoid out-of-memory crashes.
  • Fix stale diagnostics after editing visible headers.
  • Fix several crashes in the recursive include cache.
  • Fix an incorrect #include casing error on Linux.
  • Various other fixes found internally.
  • Various localization updates.
  • Fix an IntelliSense crash.
  • Update dependencies.

Instructions

The extension can be obtained by one of the methods below:

  • Install the "C/C++" or "C/C++ Extension Pack" extension published by Microsoft from the Extensions view in VS Code.
  • Download a vsix that matches your OS from the Assets section below (and install it via the method mentioned above). The previous download methods have the vsix signatures verified by the Marketplace, but for this method, you can do the verification by downloading the matching manifest and signature.p7s file and running npx [at]vscode/vsce@latest verify-signature -i <.vsix> -m <.signature.manifest> -s <.signature.p7s> vscode-vsce#1044.

Requirements

  • VS Code 1.67.0 or later (April 2022).
  • Windows 10+ (x64, arm64), macOS 10.12+, Linux (Ubuntu 16+, etc.).
    • Debugging is not supported on CentOS 7 or RHEL 7. The last supported version was 1.22.11: #13219.
    • The last supported version for Windows 7 and 8 was 1.30.5.

Changes

New Feature

  • Add support for "Run without debugging". #1201

Enhancements

  • Add a C_Cpp.doxygen.generateOnCodeAction setting to allow disabling of Doxygen generation code actions. #14341
  • Add a cpptools.waitForTagParsing command (for use by the C/C++ DevTools extension). PR #14407
  • Improve wildcard matching with the debugger natvis. MIEngine#1162
  • Add support for HideRawView with the debugger natvis. MIEngine#1458

Bug Fixes

  • Fix high CPU usage caused by repeated calls to selectChatModels. #14168, #14211, #14241
  • Fix the MSVC developer environment not working if UCRTVersion isn't found, and update the walkthrough instructions for installing MSVC. #14352
  • Fix an IntelliSense crash when three special-case comments are used in a template. #14360
  • Fix Copilot hover taking too many premium requests. #14372
  • Fix null pointers being expandable for variables in the debugger. MIEngine#698
  • Fix recursive {this} evaluation with the debugger natvis. MIEngine#1391
  • Update clang-tidy and clang-format from 22.1.1 to 22.1.3 (bug fixes).
  • Fix a bug with semantic colorization of operators.

@embedded-releaser-app embedded-releaser-app Bot added dependencies Pull requests that update a dependency file vscode-extensions labels Aug 9, 2026
@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ ACTION actionlint 24 0 0 0.59s
✅ ACTION zizmor 24 0 0 0 6.19s
✅ DOCKERFILE hadolint 3 0 0 0.97s
✅ JSON npm-package-json-lint yes no no 0.48s
✅ JSON prettier 22 3 0 0 0.73s
✅ JSON v8r 22 0 0 8.43s
✅ MARKDOWN markdownlint 12 0 0 0 0.93s
✅ MARKDOWN markdown-table-formatter 12 1 0 0 0.17s
✅ REPOSITORY checkov yes no no 27.13s
✅ REPOSITORY gitleaks yes no no 2.28s
✅ REPOSITORY git_diff yes no no 0.01s
✅ REPOSITORY grype yes no no 56.13s
✅ REPOSITORY osv-scanner yes no no 0.69s
✅ REPOSITORY secretlint yes no no 1.05s
✅ REPOSITORY syft yes no no 2.56s
✅ REPOSITORY trivy yes no no 11.4s
✅ REPOSITORY trivy-sbom yes no no 0.29s
✅ REPOSITORY trufflehog yes no no 3.38s
⚠️ SPELL lychee 86 2 0 11.07s
✅ YAML prettier 32 0 0 0 1.02s
✅ YAML v8r 32 0 0 8.05s
✅ YAML yamllint 32 0 0 0.83s

Detailed Issues

⚠️ SPELL / lychee - 2 errors
📝 Summary
---------------------
🔍 Total..........133
🔗 Unique.........112
✅ Successful.....126
⏳ Timeouts.........0
🔀 Redirected......13
👻 Excluded.........0
❓ Unknown..........0
🚫 Errors...........2
⛔ Unsupported......2

Errors in .github/TOOL_VERSION_ISSUE_TEMPLATE.md
[403] https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads (at 30:7) | Rejected status code: 403 Forbidden

Errors in README.md
[ERROR] https://docs.sigstore.dev/cosign/signing/overview/ (at 135:76) | Network error: Connection reset by peer (os error 104)

Hint: Followed 13 redirects. You might want to consider replacing redirecting URLs with the resolved URLs. Use verbose mode (`-v`/`-vv`) to see redirection details.
Hint: You can configure accepted/rejected response codes with `-a` or `--accept`

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@9.5.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,ACTION_ZIZMOR,DOCKERFILE_HADOLINT,JSON_V8R,JSON_PRETTIER,JSON_NPM_PACKAGE_JSON_LINT,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_GRYPE,REPOSITORY_OSV_SCANNER,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

@embedded-releaser-app
embedded-releaser-app Bot force-pushed the feature/embedded-devcontainer-cpp/update-vscode-extensions-devcontainer-metadata.json branch from 8bbc605 to 88af654 Compare August 16, 2026 03:26
@embedded-releaser-app
embedded-releaser-app Bot force-pushed the feature/embedded-devcontainer-cpp/update-vscode-extensions-devcontainer-metadata.json branch from 88af654 to 65a11cf Compare August 23, 2026 03:29
@embedded-releaser-app embedded-releaser-app Bot changed the title chore(deps, cpp): update sonarsource.sonarlint-vscode in devcontainer-metadata.json chore(deps, cpp): update ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer-metadata.json Aug 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file vscode-extensions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants