ci(deps): bump the github-actions group across 1 directory with 5 updates

[dependabot]

Bumps the github-actions group with 5 updates in the / directory:

Package	From	To
step-security/harden-runner	2.20.0	2.20.1
zizmorcore/zizmor-action	0.6.1	0.6.2
github/codeql-action/upload-sarif	4.37.3	4.37.6
docker/login-action	4.5.1	4.6.0
actions/attest	4.2.0	4.2.2

Updates step-security/harden-runner from 2.20.0 to 2.20.1

Release notes

Sourced from step-security/harden-runner's releases.

v2.20.1

What's Changed

• AWS CodeBuild-hosted runner support
• Implicitly allow single-labeled (internal) domains in block-mode

Full Changelog: step-security/harden-runner@v2.20.0...v2.20.1

Commits

• b09bb98 Merge pull request #680 from step-security/aws-code-build
• 35cd77b docs: document the Global Block List in the features list
• bb6dbef chore: rebuild dist with clean dependency install
• 98f73c5 chore: update eBPF agent to v1.8.14
• 54193c1 Reapply "feat(runners): detect AWS CodeBuild-hosted runners as third-party pr...
• d22dd48 Revert "fix(self-hosted): flush agent events at job end when deploy-on-self-h...
• 0ff0941 fix(self-hosted): flush agent events at job end when deploy-on-self-hosted-vm...
• a3c333d Revert "feat(runners): detect AWS CodeBuild-hosted runners as third-party pro...
• bf94c00 feat(runners): detect AWS CodeBuild-hosted runners as third-party provider
• 514522c fix(self-hosted): resolve runner user when USER env var is unset
• See full diff in compare view

Updates zizmorcore/zizmor-action from 0.6.1 to 0.6.2

Release notes

Sourced from zizmorcore/zizmor-action's releases.

v0.6.2

zizmor 1.29.0 is now the default version.

Commits

• 3dc1ecc Sync zizmor versions (#149)
• dc57e30 chore(deps): bump the github-actions group with 3 updates (#147)
• d94880a README: bump pins (#146)
• See full diff in compare view

Updates github/codeql-action/upload-sarif from 4.37.3 to 4.37.6

Release notes

Sourced from github/codeql-action/upload-sarif's releases.

v4.37.6

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

v4.37.5

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

v4.37.4

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

Changelog

Sourced from github/codeql-action/upload-sarif's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.7 - 13 Aug 2026

• Update default CodeQL bundle version to 2.26.3. #4085

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

4.36.3 - 01 Jul 2026

No user facing changes.

4.36.2 - 04 Jun 2026

... (truncated)

Commits

• 5595cca Merge pull request #4071 from github/update-v4.37.6-6a9359a1b
• ec9c757 Add change note for PR 4070
• 45c8742 Update changelog for v4.37.6
• 6a9359a Merge pull request #4070 from github/mbg/remote-address/change-file-default
• 065cdc0 Change DEFAULT_CONFIG_FILE_NAME
• f99dd5a Merge pull request #4066 from github/dependabot/npm_and_yarn/js-yaml-5.2.2
• 1804b21 Merge pull request #4068 from github/mergeback/v4.37.5-to-main-d1ba80a1
• 3020a2f Rebuild
• 93c3a5a Update changelog and version after v4.37.5
• d1ba80a Merge pull request #4067 from github/update-v4.37.5-1cd4d01d5
• Additional commits viewable in compare view

Updates docker/login-action from 4.5.1 to 4.6.0

Release notes

Sourced from docker/login-action's releases.

v4.6.0

• Harden buildx scoped config path handling by @​crazy-max in docker/login-action#1059
• Bump @​aws-sdk/client-ecr and @​aws-sdk/client-ecr-public to 3.1095.0 in docker/login-action#1051
• Bump js-yaml from 5.2.1 to 5.2.2 in docker/login-action#1057
• Bump postcss from 8.5.10 to 8.5.22 in docker/login-action#1056

Full Changelog: docker/login-action@v4.5.2...v4.6.0

v4.5.2

• Surface Docker Hub OIDC error responses by @​crazy-max in docker/login-action#1058

Full Changelog: docker/login-action@v4.5.1...v4.5.2

Commits

• dbcb813 Merge pull request #1051 from docker/dependabot/npm_and_yarn/aws-sdk-dependen...
• 5bcb015 [dependabot skip] chore: update generated content
• b30b2f2 build(deps): bump the aws-sdk-dependencies group across 1 directory with 2 up...
• 9087f1e Merge pull request #1057 from docker/dependabot/npm_and_yarn/js-yaml-5.2.2
• 0009830 [dependabot skip] chore: update generated content
• 2325523 build(deps): bump js-yaml from 5.2.1 to 5.2.2
• 4ec1d4a Merge pull request #1056 from docker/dependabot/npm_and_yarn/postcss-8.5.22
• 5fc99ba Merge pull request #1053 from docker/dependabot/github_actions/aws-actions/co...
• e512bd5 Merge pull request #1052 from docker/dependabot/github_actions/codeql-actions...
• a146c91 Merge pull request #1059 from crazy-max/harden-buildx-scope-paths
• Additional commits viewable in compare view

Updates actions/attest from 4.2.0 to 4.2.2

Release notes

Sourced from actions/attest's releases.

v4.2.2

What's Changed

• Bump @​sigstore/oci from 0.7.1 to 0.7.2 by @​bdehamer in actions/attest#469
• Bump brace-expansion by @​dependabot[bot] in actions/attest#468
• Bump ip-address from 10.2.0 to 10.4.0 by @​dependabot[bot] in actions/attest#467

Full Changelog: actions/attest@v4.2.1...v4.2.2

v4.2.1

What's Changed

• Bump tar from 7.5.17 to 7.5.21 by @​dependabot[bot] in actions/attest#459
• fix: strip OCI image tag when pushing attestation to registry by @​bdehamer in actions/attest#464

Full Changelog: actions/attest@v4.2.0...v4.2.1

Commits

• 1e69f48 Bump ip-address from 10.2.0 to 10.4.0 (#467)
• 02787ce Bump brace-expansion (#468)
• 98ac037 bump @​sigstore/oci from 0.7.1 to 0.7.2 (#469)
• 508db95 fix: strip OCI image tag when pushing attestation to registry (#464)
• dda48f2 Bump the npm-development group across 1 directory with 6 updates (#461)
• 7d789a3 Bump the actions-minor group with 3 updates (#463)
• 1f3ca2f Add release-cutter canvas extension (#454)
• d215549 Bump tar from 7.5.17 to 7.5.21 (#459)
• 20c90ed Bump the npm-development group with 2 updates (#455)
• 43c2c81 Bump the actions-minor group with 4 updates (#456)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Test Results

 25 files  ±0   25 suites  ±0   18m 40s ⏱️ - 1m 18s
 48 tests ±0   48 ✅ ±0  0 💤 ±0  0 ❌ ±0 
209 runs  ±0  209 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 1151821. ± Comparison against base commit 591db7c.

♻️ This comment has been updated with latest results.

[github-actions]

✅⚠️MegaLinter analysis: Success with warnings

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	23		0	0	0.22s
✅ DOCKERFILE	hadolint	4		0	0	0.34s
✅ JSON	npm-package-json-lint	yes		no	no	0.45s
✅ JSON	prettier	45	8	0	0	0.9s
✅ JSON	v8r	45		0	0	16.48s
✅ MARKDOWN	markdownlint	13	0	0	0	1.19s
✅ MARKDOWN	markdown-table-formatter	13	0	0	0	0.27s
✅ REPOSITORY	betterleaks	yes		no	no	1.16s
✅ REPOSITORY	checkov	yes		no	no	29.0s
✅ REPOSITORY	gitleaks	yes		no	no	1.08s
✅ REPOSITORY	git_diff	yes		no	no	0.02s
✅ REPOSITORY	grype	yes		no	no	74.33s
⚠️ REPOSITORY	osv-scanner	yes		2	no	0.74s
✅ REPOSITORY	secretlint	yes		no	no	2.15s
✅ REPOSITORY	syft	yes		no	no	2.65s
✅ REPOSITORY	trivy	yes		no	no	12.07s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.33s
✅ REPOSITORY	trufflehog	yes		no	no	6.63s
⚠️ SPELL	lychee	117		4	0	37.23s
✅ YAML	prettier	36	0	0	0	1.23s
✅ YAML	v8r	36		0	0	14.29s
✅ YAML	yamllint	36		0	0	1.19s

Detailed Issues

⚠️ SPELL / lychee - 4 errors

📝 Summary
---------------------
🔍 Total..........154
🔗 Unique.........126
✅ Successful.....145
⏳ Timeouts.........0
🔀 Redirected......19
👻 Excluded.........0
❓ Unknown..........0
🚫 Errors...........4
⛔ Unsupported......4

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

Errors in README.md
[ERROR] https://docs.sigstore.dev/cosign/signing/overview/ (at 156:76) | Network error: Connection reset by peer (os error 104)
[ERROR] https://docs.sigstore.dev/cosign/verifying/verify/ (at 158:22) | Network error: Connection reset by peer (os error 104)
[ERROR] https://www.conventionalcommits.org/en/v1.0.0/ (at 212:88) | Network error: Connection reset by peer (os error 104)

Hint: Followed 19 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`

⚠️ REPOSITORY / osv-scanner - 2 errors

Scanning dir .
Starting filesystem walk for root: /
Scanned package-lock.json file and found 73 packages
Scanned test/rust/workspace/cargo/Cargo.lock file and found 1 package
Scanned test/rust/workspace/test/Cargo.lock file and found 1 package
Scanned test/rust/workspace/clippy/Cargo.lock file and found 1 package
Scanned test/embedded-rust/workspace/cortex-mf/Cargo.lock file and found 20 packages
Scanned test/embedded-rust/workspace/cortex-m/Cargo.lock file and found 20 packages
Scanned .devcontainer/docs/requirements.txt file and found 14 packages
Scanned .devcontainer/cpp/requirements.txt file and found 20 packages
End status: 141 dirs visited, 493 inodes visited, 8 Extract calls, 41.586324ms elapsed, 41.586454ms wall time

Total 3 packages affected by 4 known vulnerabilities (0 Critical, 2 High, 0 Medium, 0 Low, 2 Unknown) from 2 ecosystems.
2 vulnerabilities can be fixed.

+-------------------------------------+------+-----------+-----------------------+---------+---------------+---------------------------------------------------+
| OSV URL                             | CVSS | ECOSYSTEM | PACKAGE               | VERSION | FIXED VERSION | SOURCE                                            |
+-------------------------------------+------+-----------+-----------------------+---------+---------------+---------------------------------------------------+
| https://osv.dev/RUSTSEC-2026-0110   |      | crates.io | bare-metal            | 0.2.5   | --            | test/embedded-rust/workspace/cortex-m/Cargo.lock  |
| https://osv.dev/RUSTSEC-2026-0110   |      | crates.io | bare-metal            | 0.2.5   | --            | test/embedded-rust/workspace/cortex-mf/Cargo.lock |
| https://osv.dev/GHSA-mh99-v99m-4gvg | 7.5  | npm       | brace-expansion (dev) | 5.0.7   | 5.0.8         | package-lock.json                                 |
| https://osv.dev/GHSA-rgw5-rvv9-x895 | 7.5  | npm       | brace-expansion (dev) | 5.0.7   | 5.0.9         | package-lock.json                                 |
+-------------------------------------+------+-----------+-----------------------+---------+---------------+---------------------------------------------------+

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:

• oxsecurity/megalinter/flavors/salesforce@v9.6.0 (57 linters)
• oxsecurity/megalinter/flavors/javascript@v9.6.0 (63 linters)

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.6.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,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_BETTERLEAKS,REPOSITORY_GRYPE,REPOSITORY_OSV_SCANNER,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-base:edge ➔ ghcr.io/philips-software/amp-devcontainer-base:pr-1421

📈 Size Comparison Table

OS/Platform	Previous	Current	Change	Trend
linux/amd64	89.03 MB	89.03 MB	613 B (0%)	🔽
linux/arm64	87.07 MB	87.07 MB	+750 B (+0%)	🔼

[github-actions]

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-docs:edge ➔ ghcr.io/philips-software/amp-devcontainer-docs:pr-1421

📈 Size Comparison Table

OS/Platform	Previous	Current	Change	Trend
linux/amd64	220.43 MB	220.43 MB	585 B (0%)	🔽
linux/arm64	216.75 MB	216.75 MB	+548 B (+0%)	🔼

[github-actions]

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-embedded-rust:edge ➔ ghcr.io/philips-software/amp-devcontainer-embedded-rust:pr-1421

📈 Size Comparison Table

OS/Platform	Previous	Current	Change	Trend
linux/amd64	511.63 MB	511.63 MB	76 B (0%)	🔽
linux/arm64	461.31 MB	461.31 MB	+1.05 kB (+0%)	🔼

[github-actions]

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-rust:edge ➔ ghcr.io/philips-software/amp-devcontainer-rust:pr-1421

📈 Size Comparison Table

OS/Platform	Previous	Current	Change	Trend
linux/amd64	444.95 MB	444.95 MB	861 B (0%)	🔽
linux/arm64	394.93 MB	394.93 MB	+1.75 kB (+0%)	🔼

[github-actions]

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-cpp:edge ➔ ghcr.io/philips-software/amp-devcontainer-cpp:pr-1421

📈 Size Comparison Table

OS/Platform	Previous	Current	Change	Trend
linux/amd64	409.14 MB	409.14 MB	+267 B (+0%)	🔼
linux/arm64	389.67 MB	389.67 MB	+1.03 kB (+0%)	🔼

[github-actions]

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-embedded-cpp:edge ➔ ghcr.io/philips-software/amp-devcontainer-embedded-cpp:pr-1421

📈 Size Comparison Table

OS/Platform	Previous	Current	Change	Trend
linux/amd64	611.32 MB	611.32 MB	+1.45 kB (+0%)	🔼
linux/arm64	591.04 MB	591.04 MB	+1.13 kB (+0%)	🔼

[github-actions]

Pull Request Report (#1421)

Static measures

Description	Value
Number of added lines	35
Number of deleted lines	35
Number of changed files	21
Number of commits	2
Number of reviews	1
Number of comments (w/o review comments)	9
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	5

Time related measures

Description	Value
PR lead time (from creation to close of PR)	9 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	9 Days
Time to merge after last review	25.5 Min

Status check related measures

Description	Value
Total runtime for last status check run (Workflow for PR)	1.5 Hours
Total time spend in last status check run on PR	20.8 Min

[github-actions]

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