Skip to content

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

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

chore(deps, cpp): update ms-vscode.cpptools in devcontainer-metadata.json#1152
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.4 to 1.30.5

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

  • Fix a potential language server deadlock after editing code.

@philips-software-forest-releaser philips-software-forest-releaser bot added dependencies Pull requests that update a dependency file vscode-extensions labels Feb 15, 2026
@philips-software-forest-releaser philips-software-forest-releaser bot requested a review from a team as a code owner February 15, 2026 03:31
@sonarqubecloud
Copy link

@github-actions
Copy link
Contributor

⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ ACTION actionlint 21 0 0 0.61s
✅ DOCKERFILE hadolint 3 0 0 0.81s
✅ GHERKIN gherkin-lint 6 0 0 2.65s
✅ JSON npm-package-json-lint yes no no 0.5s
✅ JSON prettier 21 4 0 0 0.69s
✅ JSON v8r 21 0 0 7.56s
✅ MARKDOWN markdownlint 12 0 0 0 1.06s
✅ MARKDOWN markdown-table-formatter 12 0 0 0 0.27s
✅ REPOSITORY checkov yes no no 18.19s
✅ REPOSITORY gitleaks yes no no 0.63s
✅ REPOSITORY git_diff yes no no 0.01s
⚠️ REPOSITORY grype yes no 20 30.45s
✅ REPOSITORY secretlint yes no no 1.06s
✅ REPOSITORY syft yes no no 2.07s
✅ REPOSITORY trivy yes no no 5.86s
✅ REPOSITORY trivy-sbom yes no no 0.22s
✅ REPOSITORY trufflehog yes no no 2.2s
⚠️ SPELL lychee 81 1 0 21.71s
✅ YAML prettier 29 0 0 0 0.97s
✅ YAML v8r 29 0 0 8.61s
✅ YAML yamllint 29 0 0 0.69s

Detailed Issues

⚠️ REPOSITORY / grype - 20 warnings
warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/continuous-integration.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/image-cleanup.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/issue-cleanup.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/issue-creation-tool-versions.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/linting-formatting.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/ossf-scorecard.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/pr-conventional-title.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/pr-image-cleanup.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/pr-report.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/release-build.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/release-please.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/update-dependencies.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/vulnerability-scan.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/wc-acceptance-test.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/wc-build-push.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/wc-dependency-review.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/wc-document-generation.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/wc-integration-test.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/wc-publish-templates.yml

warning: A medium vulnerability in github-action package: step-security/harden-runner, version v2.14.1 was found at: /.github/workflows/wc-sanitize-image-name.yml

warning: 20 warnings emitted
⚠️ SPELL / lychee - 1 error
[403] https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads | Network error: Forbidden
[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)
[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

📦 Container Size Analysis

Note

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

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 174.05 MB 174.05 MB 205 B (0%) 🔽
linux/arm64 166.57 MB 166.57 MB 53 B (0%) 🔽

@github-actions
Copy link
Contributor

📦 Container Size Analysis

Note

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

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 695.76 MB 695.76 MB 98 B (0%) 🔽
linux/arm64 676.63 MB 676.63 MB 299 B (0%) 🔽

@github-actions
Copy link
Contributor

github-actions bot commented Feb 15, 2026

Test Results

2 files   -  5  2 suites   - 5   0s ⏱️ - 4m 0s
1 tests  - 32  1 ✅  - 32  0 💤 ±0  0 ❌ ±0 
2 runs   - 67  2 ✅  - 67  0 💤 ±0  0 ❌ ±0 

Results for commit e4a5d68. ± Comparison against base commit 449ed74.

♻️ This comment has been updated with latest results.

@rjaegers Ron (rjaegers) added this pull request to the merge queue Feb 16, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 16, 2026
@rjaegers Ron (rjaegers) added this pull request to the merge queue Feb 17, 2026
Merged via the queue into main with commit 6a57e1b Feb 17, 2026
64 of 69 checks passed
@rjaegers Ron (rjaegers) deleted the feature/amp-devcontainer-cpp/update-vscode-extensions-devcontainer-metadata.json branch February 17, 2026 10:30
@github-actions
Copy link
Contributor

Pull Request Report (#1152)

Static measures

Description Value
Number of added lines 1
Number of deleted lines 1
Number of changed files 1
Number of commits 1
Number of reviews 1
Number of comments (w/o review comments) 5
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.3 Days
Time that was spend on the branch before the PR was created 3 Sec
Time that was spend on the branch before the PR was merged 2.3 Days
Time to merge after last review 1 Days

Status check related measures

Description Value
Total runtime for last status check run (Workflow for PR) 25.9 Min
Total time spend in last status check run on PR 2.2 Days

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