Skip to content

chore(deps, cpp): update ms-vscode.cmake-tools, ms-vscode.cpptools in devcontainer-metadata.json#1144

Merged
Ron (rjaegers) merged 1 commit intomainfrom
feature/amp-devcontainer-cpp/update-vscode-extensions-devcontainer-metadata.json
Feb 10, 2026
Merged

chore(deps, cpp): update ms-vscode.cmake-tools, ms-vscode.cpptools in devcontainer-metadata.json#1144
Ron (rjaegers) merged 1 commit intomainfrom
feature/amp-devcontainer-cpp/update-vscode-extensions-devcontainer-metadata.json

Conversation

@philips-software-forest-releaser
Copy link
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 ms-vscode.cpptools from 1.30.3 to 1.30.4

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.67.0 or later (April 2022).
  • Windows 7+ (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.

Change

Bug Fix

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 7+ (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.

Changes

Enhancements

  • Add IntelliSense support for C++23 multidimensional subscript operators. #11400, #13798
  • Change C completion behavior to automatically trigger after the struct/union/enum keyword and to filter based on the keyword. #13634
  • Add IntelliSense support for C23/C++26 #embed. #13705
  • Change C++ completions after using namespace to include only namespaces and namespace aliases. #14091
  • Add IntelliSense support for C++23 static operator[].

Bug Fixes

  • Fix C_Cpp.commentContinuationPatterns not working after the 2nd line (for non-/** patterns). #8998
  • Fix ${userHome} not resolving in C_Cpp path settings. #10350
  • Fix the Locals/Watch window displaying std::map<enum, struct> incorrectly when using the cppdbg debugger. #12102
  • Fix an incorrect IntelliSense error on an overridden method. #13729
  • Fix an IntelliSense error with std::countl_zero. #13876
  • Fix an IntelliSense squiggle on the wrong identifier when assigning to a constant member variable. #14018
  • Fix IntelliSense with Clang mode C++23 deduced type construction with auto. #14041
  • Fix a long args list in launch.json getting truncated when using the cppdbg debugger. #14054
  • Fix changes to C_Cpp.commentContinuationPatterns not taking effect until the extension restarts. #14079
  • Fix C_Cpp.commentContinuationPatterns not working correctly for a pattern if it's a prefix of a pattern that is later in the list. #14081
  • Fix completion not automatically triggering if invoked on the last column of a line when the previous token is an identifier. #14086
  • Fix an IntelliSense error with std::popcount. #14105
  • Fix GitHub Copilot hover. #14114
  • Fix headers sometimes using a header-only configuration from a configuration provider instead of the source file's configuration. #14126
  • Fix a reference in a #define not being found if it's directly after a #include. #14130
  • Fix a bug that could cause IntelliSense operations to fail when a document is closed during processing.
  • Fix an IntelliSense crash in a_completion_symbol_manager::handle_function when Copilot is enabled.
  • Fix a bug with internal buffer handling that could cause some IntelliSense operations to fail.

Updates ms-vscode.cmake-tools from 1.22.26 to 1.22.27

Release notes

Features:

Improvements:

  • In the Test Explorer, associate CTest tests with outermost function or macro invocation that calls add_test() instead of with the add_test() call itself. #4490 @malsyned
  • Better support of cmake v4.1 and its error index files in cmake-file-api replies #4575 Contributed by STMicroelectronics
  • Added support for clang-cl vendor detection: ${buildKitVendor}, ${buildKitVersionMajor}, etc. now expand correctly when using clang-cl on Windows #4524 @wchou158

Bug Fixes:

  • Fix Compiler Warnings not shown in Problems Window [#4567]https://www.github.com/microsoft/vscode-cmake-tools/issues/4567
  • Fix bug in which clicking "Run Test" for filtered tests executed all tests instead #4501 @hippo91
  • Migrate macOS CI from deprecated macOS-13 to macOS-15 Image #4633
  • Ensure Visual Studio developer environment propagation preserves VCPKG_ROOT, enabling vcpkg-dependent configure runs after using the Set Visual Studio Developer Environment command. microsoft/vscode-cpptools#14083
  • Fix auto-focusing the "Search" input field in the CMake Cache view. #4552 @simhof-basyskom
  • Remove the demangling feature in the code coverage implementation for now since it doesn't work properly. PR #4658
  • Fix incorrect IntelliSense configuration when a UTILITY has source files. #4404

@philips-software-forest-releaser philips-software-forest-releaser bot added the dependencies Pull requests that update a dependency file label Feb 8, 2026
@philips-software-forest-releaser philips-software-forest-releaser bot requested a review from a team as a code owner February 8, 2026 03:38
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 8, 2026

@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2026

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-base:edgeghcr.io/philips-software/amp-devcontainer-base:pr-1144

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 174.05 MB 174.05 MB 752 B (0%) 🔽
linux/arm64 166.57 MB 166.57 MB +14 B (+0%) 🔼

@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2026

⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ ACTION actionlint 21 0 0 0.5s
✅ DOCKERFILE hadolint 3 0 0 0.69s
✅ GHERKIN gherkin-lint 6 0 0 2.41s
✅ JSON npm-package-json-lint yes no no 0.48s
✅ JSON prettier 21 4 0 0 0.52s
✅ JSON v8r 21 0 0 6.6s
✅ MARKDOWN markdownlint 12 0 0 0 0.93s
✅ MARKDOWN markdown-table-formatter 12 0 0 0 0.22s
✅ REPOSITORY checkov yes no no 17.68s
✅ REPOSITORY gitleaks yes no no 0.52s
✅ REPOSITORY git_diff yes no no 0.01s
✅ REPOSITORY grype yes no no 28.56s
✅ REPOSITORY secretlint yes no no 0.91s
✅ REPOSITORY syft yes no no 1.81s
✅ REPOSITORY trivy yes no no 7.92s
✅ REPOSITORY trivy-sbom yes no no 0.23s
✅ REPOSITORY trufflehog yes no no 2.24s
⚠️ SPELL lychee 81 1 0 21.79s
✅ YAML prettier 29 0 0 0 0.96s
✅ YAML v8r 29 0 0 7.92s
✅ YAML yamllint 29 0 0 0.84s

Detailed Issues

⚠️ SPELL / lychee - 1 error
[IGNORED] docker://pandoc/extra:3.7.0@sha256:a703d335fa237f8fc3303329d87e2555dca5187930da38bfa9010fa4e690933a | Unsupported: Error creating request client: builder error for url (docker://pandoc/extra:3.7.0@sha256:a703d335fa237f8fc3303329d87e2555dca5187930da38bfa9010fa4e690933a)
[403] https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads | Network error: Forbidden
[IGNORED] https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/philips-software/amp-devcontainer | Unsupported: Error creating request client: builder error for url (vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/philips-software/amp-devcontainer)
📝 Summary
---------------------
🔍 Total..........126
✅ Successful.....123
⏳ Timeouts.........0
🔀 Redirected.......0
👻 Excluded.........0
❓ Unknown..........0
🚫 Errors...........1

Errors in .github/TOOL_VERSION_ISSUE_TEMPLATE.md
[403] https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads | Network error: Forbidden

See detailed reports in MegaLinter artifacts

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.3.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,DOCKERFILE_HADOLINT,GHERKIN_GHERKIN_LINT,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_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

@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2026

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-rust:edgeghcr.io/philips-software/amp-devcontainer-rust:pr-1144

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 554.46 MB 554.46 MB 993 B (0%) 🔽
linux/arm64 508.69 MB 508.69 MB 13 B (0%) 🔽

@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2026

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-cpp:edgeghcr.io/philips-software/amp-devcontainer-cpp:pr-1144

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 695.77 MB 695.76 MB 1.78 kB (0%) 🔽
linux/arm64 676.63 MB 676.63 MB +808 B (+0%) 🔼

@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2026

Test Results

 6 files   - 1   6 suites   - 1   2m 38s ⏱️ - 1m 17s
32 tests  - 1  32 ✅  - 1  0 💤 ±0  0 ❌ ±0 
68 runs   - 1  68 ✅  - 1  0 💤 ±0  0 ❌ ±0 

Results for commit f509186. ± Comparison against base commit 558e7e8.

@rjaegers Ron (rjaegers) added this pull request to the merge queue Feb 10, 2026
Merged via the queue into main with commit 84f3450 Feb 10, 2026
48 of 49 checks passed
@rjaegers Ron (rjaegers) deleted the feature/amp-devcontainer-cpp/update-vscode-extensions-devcontainer-metadata.json branch February 10, 2026 07:33
@github-actions
Copy link
Contributor

Pull Request Report (#1144)

Static measures

Description Value
Number of added lines 2
Number of deleted lines 2
Number of changed files 1
Number of commits 1
Number of reviews 1
Number of comments (w/o review comments) 6
Number of reviews that contains a comment to resolve 0
Number of reviews that requested a change from the author 0
Number of reviews that approved the Pull Request 1
Get the total number of participants of a Pull Request 4

Time related measures

Description Value
PR lead time (from creation to close of PR) 2.2 Days
Time that was spend on the branch before the PR was created 2 Sec
Time that was spend on the branch before the PR was merged 2.2 Days
Time to merge after last review 17.5 Min

Status check related measures

Description Value
Total runtime for last status check run (Workflow for PR) 43.9 Min
Total time spend in last status check run on PR 16.8 Min

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.

1 participant