Skip to content

chore(deps, cpp): update llvm-vs-code-extensions.vscode-clangd, matepek.vscode-catch2-test-adapter, ms-vscode.cmake-tools, ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer-metadata-vscode.json - #34

Merged
gabrielfrasantos merged 1 commit into
mainfrom
feature/embedded-devcontainer-cpp/update-vscode-extensions
Mar 29, 2026
Merged

chore(deps, cpp): update llvm-vs-code-extensions.vscode-clangd, matepek.vscode-catch2-test-adapter, ms-vscode.cmake-tools, ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer-metadata-vscode.json#34
gabrielfrasantos merged 1 commit into
mainfrom
feature/embedded-devcontainer-cpp/update-vscode-extensions

Conversation

@embedded-releaser-app

@embedded-releaser-app embedded-releaser-app Bot commented Mar 22, 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 4.31.0 to 4.45.0

Release notes
  • Update Java analyzer 8.24 -> 8.26
  • Update Python analyzer 5.18 -> 5.19
  • Update PHP analyzer 3.54 -> 3.55
  • Update Text & Secrets analyzer 2.38 -> 2.41

  • Update C# analyzer 10.19 -> 10.20

  • Update Java analyzer 8.23 -> 8.24

  • Update Python analyzer 5.17 -> 5.18

  • Upadte XML analyzer 2.15 to 2.16

  • Update JS/TS/CSS analyzer 11.8 -> 12.0

  • Update C# analyzer 10.18 -> 10.19

  • Update Python analyzer 5.16 -> 5.17

  • Update Go analyzer 1.32 -> 1.33

  • Update IaC analyzer 2.5 -> 2.6.1

  • Update CFamily analyzer 6.77 -> 6.78

  • Introduce Remediation Center - an experimental feature available inside SonarQube for IDE Labs. It streamlines your remediation workflow by bringing SonarQube (Server, Cloud) actions directly within a new IDE panel

  • Update JS/TS/CSS analyzer 11.7 -> 11.8

  • Update Java analyzer 8.22 -> 8.23

Bugfixes and technical improvements

  • Update Text & Secrets analyzer 2.36 -> 2.38

  • Update CFamily analyzer 6.76 -> 6.77

  • Upadte XML analyzer 2.14.2 to 2.15

  • Update IaC analyzer 2.3 -> 2.5

  • Update PHP analyzer 3.53 -> 3.54

  • Update Go analyzer 1.31 -> 1.32

  • Update C# analyzer 10.17 -> 10.18

  • Bugfix - Can't setup SonarQube Cloud connection when there are many organisations to pick from

  • Enable AI Agent configurations for Kiro

  • Capture data locally with flight recorder

  • Update Python analyzer 5.15 -> 5.16

  • Bugfix - unable to verify authenticity of the downloaded CFamily analyzer

  • Update Python analyzer 5.14.2 -> 5.15

  • Update CFamily analyzer 6.75.1 -> 6.76

  • Update Text & Secrets analyzer 2.34 -> 2.36

  • Update C# analyzer 10.16.2 -> 10.17

  • Update IaC analyzer 2.2 -> 2.3

  • Update CFamily analyzer 6.73 -> 6.74

  • Update IaC analyzer 1.52 -> 2.1

  • Update JS/TS/CSS analyzer 11.5 -> 11.6

  • Update Python analyzer 5.12 -> 5.13

  • Update PHP analyzer 3.51 -> 3.52

  • Update Go analyzer 1.29 -> 1.30

  • Update Text & Secrets analyzer 2.32 -> 2.33

  • Support .slnx projects

  • Support one-click generation of Windsurf Cascade hooks for post-generation analysis (beta)

  • Stop packaging OmniSharp in platform-specific builds on OpenVSX marketplace. As a workaround, download and install plugin from our releases page to keep analyzing C# code on non-Microsoft IDEs.

  • Update IaC analyzer 1.51 -> 1.52

  • Update Go analyzer 1.28 -> 1.29

  • Update Java analyzer 8.19 -> 8.20

  • Update Text & Secrets analyzer 2.31 -> 2.32

  • Update IaC analyzer 1.50 -> 1.51

  • Update PHP analyzer 3.49 -> 3.50 -> 3.51

  • Update Text & Secrets analyzer 2.30 -> 2.31

  • Update HTML analyzer 3.19 -> 3.20

  • Update Python analyzer 5.11 -> 5.12

  • Update JS/TS/CSS analyzer 11.4 -> 11.5, 58 new QuickFixes

  • Allow one-click installation of SonarQube MCP Server

Update JS/TS/CSS analyzer 11.3 -> 11.4 -> 11.4.1, Update Node.js min required versions to "^20.12.0 || >=22.11.0"
Update IaC analyzer 1.49 -> 1.50
Update Go analyzer 1.27 -> 1.28
Update Text & Secrets analyzer 2.28 -> 2.29 -> 2.30
Update Python analyzer 5.9 -> 5.10 -> 5.11
Update CFamily analyzer 6.71 -> 6.72 -> 6.73
Update Java analyzer 8.18 -> 8.19

Updates ms-vscode.cpptools from 1.27.7 to 1.31.3

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.

Changes

Enhancements

  • Add support for program in attach debug configurations. #14046
  • Remove unnecessary console.debug logging. #14294
  • Update clang-tidy and clang-format from 21.1.4 to 22.1.1.
  • Update support for the latest compiler versions.
  • Update SQLite to the latest version.

Bug Fixes

  • Fix an IntelliSense error with deducing this (explicit object member functions) with conversion operators. #14140
  • Fix embed-dir compiler arguments not being handled for IntelliSense. #14154
  • Fix workspace symbol search with scope::variable not working after symbols are deleted and then added back. #14200
  • Fix bugs where a path was checked for existence but not whether it was a file or a folder. #14257
  • Fix the Call Hierarchy Callers Of progress UI not showing. #14287
  • Fix an IntelliSense crash when using GCC 16 span and string. #14309
  • Fix _CONTROL_FLOW_GUARD not being defined when /guard:cf is used in MSVC mode. #14310
  • Add IntelliSense support for __builtin_is_implicit_lifetime.
  • Fix three IntelliSense process crashes.
  • Fix some missing translations.

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

  • Fix a potential language server deadlock after editing code.

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.

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

  • Remove NETFXSDKDir from the developer environment check. #14084

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

New Feature

  • Enable setting the VS developer environment without running VS Code from the developer command prompt. #4742

Enhancements

  • Add built-in file associations for C++ extensionless system headers and set C_Cpp.autoAddFileAssociations to false by default. #4077
  • Add IntelliSense support for c23 enums with an underlying type. #13675

Bug Fixes

  • Fix 'Find All References' and 'Rename' on #define macro definitions. #6194
  • Fix anonymous enums not working in gcc/clang modes. #10436
  • Fix Doxygen comments at the end of a function. #13725
  • Fix mac framework search path detection to include paths passed in the includePath from a configuration provider, and fix omission of unpopulated Mac framework paths. #13993
  • Fix formatting with clang-tidy randomly getting stuck on Windows (on a call to GetOverlappedResult). #14025
  • Fix IntelliSense with MSVC mode C++23 deduced type construction with auto. #14041
  • Fix code analysis re-running automatically after a settings change when diagnostics already exist if it was manually instead of automatically invoked.
  • Reduce the memory usage in a couple cases to reduce the chance of a bad_alloc in cpptools.
  • Update clang-format and clang-tidy from 21.1.3 to 21.1.4 (fixes some formatting bugs).
  • Fix the handling of the cl.exe /external:I argument for IntelliSense configuration.
  • Fix a case where a large file could cause a bad_alloc in cpptools-srv on Windows.
  • Update the default compiler search to include newer versions of clang/gcc.
  • Fix a potential memory corruption crash of cpptools-srv (related to PCH).
  • Fix a crash in detect_encoding.

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 c23 bool, true, and false. #13737
  • Add missing C/C++ keyword completions for newer language standards. #13982
  • Update the bundled clang-tidy and clang-format from 20.1.7 to 21.1.3.

Bug Fixes

  • Fix cpptools getting stuck when clang-format is invoked on a file in a .clang-format-ignore. #13937
  • Fix the C/C++ Properties Schema Reference link in the configuration UI editor. #13949
  • Fix a crash with preReleaseCheck. #13953
  • Fix extension activation getting stuck when certain SSH config files are processed (by the SSH targets view feature). #13966
  • Fix document symbols randomly showing previous versions of symbols after they are modified. #13967
  • Prevent tag parsing of .js files to avoid a crash. #13980
  • Fix some invalid assumptions for cppbuild tasks. PR #13989
  • Fix a random crash after changing settings while code analysis is running.
  • Fix a random memory corruption and deadlock (involving task_deque).
  • A potential fix for a crash (involving line_offset_t).

Updates ms-vscode.cmake-tools from 1.21.36 to 1.22.28

Release notes

Improvements:

  • Updated extension dependencies (ms-vscode.cpp-devtools)

Bug Fixes:

Fix infinite presets reloading loop when preset files are symlinks or include symlinked files. https://www.github.com/microsoft/vscode-cmake-tools/issues/4668
Reapplying "Refactor and improve colorization language services support" https://www.github.com/microsoft/vscode-cmake-tools/pull/4697

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

Updates matepek.vscode-catch2-test-adapter from 4.17.6 to 4.22.3

Release notes

See CHANGELOG.md for details.

See CHANGELOG.md for details.

See CHANGELOG.md for details.

See CHANGELOG.md for details.

See CHANGELOG.md for details.

See CHANGELOG.md for details.

See CHANGELOG.md for details.

See CHANGELOG.md for details.

See CHANGELOG.md for details.

Updates llvm-vs-code-extensions.vscode-clangd from 0.2.0 to 0.4.0

Release notes

@embedded-releaser-app embedded-releaser-app Bot added dependencies Pull requests that update a dependency file vscode-extensions labels Mar 22, 2026
@embedded-releaser-app
embedded-releaser-app Bot force-pushed the feature/embedded-devcontainer-cpp/update-vscode-extensions branch from edc90c0 to 959cbd3 Compare March 22, 2026 03:29
@embedded-releaser-app embedded-releaser-app Bot changed the title chore(deps, cpp): update llvm-vs-code-extensions.vscode-clangd, matepek.vscode-catch2-test-adapter, ms-vscode.cmake-tools, ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer-metadata-vscode.json chore(deps, cpp): update github.vscode-github-actions, github.vscode-pull-request-github, sonarsource.sonarlint-vscode in devcontainer.json Mar 22, 2026
@github-actions

github-actions Bot commented Mar 22, 2026

Copy link
Copy Markdown
Contributor

Test Results

 4 files   4 suites   2m 7s ⏱️
30 tests 30 ✅ 0 💤 0 ❌
64 runs  64 ✅ 0 💤 0 ❌

Results for commit 4e0d22b.

♻️ This comment has been updated with latest results.

@github-actions

github-actions Bot commented Mar 22, 2026

Copy link
Copy Markdown
Contributor

⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ ACTION actionlint 19 0 0 0.62s
✅ DOCKERFILE hadolint 2 0 0 0.93s
✅ GHERKIN gherkin-lint 6 0 0 2.52s
✅ JSON npm-package-json-lint yes no no 0.49s
✅ JSON prettier 16 2 0 0 0.67s
✅ JSON v8r 16 0 0 7.59s
⚠️ MARKDOWN markdownlint 9 0 1 0 0.93s
✅ MARKDOWN markdown-table-formatter 9 1 0 0 0.25s
✅ REPOSITORY gitleaks yes no no 1.2s
✅ REPOSITORY git_diff yes no no 0.02s
⚠️ REPOSITORY grype yes no 2 31.84s
✅ REPOSITORY secretlint yes no no 0.97s
✅ REPOSITORY syft yes no no 2.0s
✅ REPOSITORY trivy yes no no 5.69s
✅ REPOSITORY trivy-sbom yes no no 0.24s
✅ REPOSITORY trufflehog yes no no 2.4s
✅ SPELL lychee 70 0 0 21.63s
✅ YAML prettier 25 0 0 0 1.29s
✅ YAML v8r 25 0 0 8.58s
✅ YAML yamllint 25 0 0 0.88s

Detailed Issues

⚠️ REPOSITORY / grype - 2 warnings
note: A low vulnerability in python package: pygments, version 2.17.2 was found at: /.devcontainer/cpp/requirements.txt

warning: A medium vulnerability in python package: requests, version 2.32.4 was found at: /.devcontainer/cpp/requirements.txt

warning: 1 warnings emitted
⚠️ MARKDOWN / markdownlint - 1 error
.github/CONTRIBUTING.md:18:7 MD051/link-fragments Link fragments should be valid [Context: "[Found a security vulnerability?](#found-a-security-vulnerability)"]

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.0.1 --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_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

github-actions Bot commented Mar 27, 2026

Copy link
Copy Markdown
Contributor

📦 Container Size Analysis

Note

Comparing gabrielfrasantos/embedded-devcontainer-rust:edgegabrielfrasantos/embedded-devcontainer-rust:pr-34

📈 Size Comparison Table

OS/Platform Previous Current Change Trend

@github-actions

github-actions Bot commented Mar 27, 2026

Copy link
Copy Markdown
Contributor

📦 Container Size Analysis

Note

Comparing gabrielfrasantos/embedded-devcontainer-cpp:edgegabrielfrasantos/embedded-devcontainer-cpp:pr-34

📈 Size Comparison Table

OS/Platform Previous Current Change Trend

…est-adapter, ms-vscode.cmake-tools, ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer-metadata-vscode.json
@embedded-releaser-app
embedded-releaser-app Bot force-pushed the feature/embedded-devcontainer-cpp/update-vscode-extensions branch from 7756f4c to bc5446c Compare March 29, 2026 03:38
@embedded-releaser-app embedded-releaser-app Bot changed the title chore(deps, cpp): update github.vscode-github-actions, github.vscode-pull-request-github, sonarsource.sonarlint-vscode in devcontainer.json chore(deps, cpp): update github.vscode-github-actions, github.vscode-pull-request-github, ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer.json Mar 29, 2026
@embedded-releaser-app
embedded-releaser-app Bot force-pushed the feature/embedded-devcontainer-cpp/update-vscode-extensions branch from bc5446c to 4e0d22b Compare March 29, 2026 03:38
@embedded-releaser-app embedded-releaser-app Bot changed the title chore(deps, cpp): update github.vscode-github-actions, github.vscode-pull-request-github, ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer.json chore(deps, cpp): update llvm-vs-code-extensions.vscode-clangd, matepek.vscode-catch2-test-adapter, ms-vscode.cmake-tools, ms-vscode.cpptools, sonarsource.sonarlint-vscode in devcontainer-metadata-vscode.json Mar 29, 2026
@gabrielfrasantos
gabrielfrasantos merged commit c289534 into main Mar 29, 2026
31 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Pull Request Report (#34)

Static measures

Description Value
Number of added lines 5
Number of deleted lines 5
Number of changed files 1
Number of commits 1
Number of reviews 0
Number of comments (w/o review comments) 4
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 0
Get the total number of participants of a Pull Request 2

Time related measures

Description Value
PR lead time (from creation to close of PR) 7.3 Days
Time that was spend on the branch before the PR was created 0 Sec
Time that was spend on the branch before the PR was merged 8.2 Hours
Time to merge after last review 0 Sec

Status check related measures

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

@github-actions

Copy link
Copy Markdown
Contributor

🎉 Hooray! The changes in this pull request went live with the release of v7.0.1 🎉

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