[dependabot]

Bumps the patch-minor-action-updates group with 2 updates: oxsecurity/megalinter/flavors/c_cpp and github/codeql-action/upload-sarif.

Updates oxsecurity/megalinter/flavors/c_cpp from 10.1.0 to 10.2.0

Release notes

Sourced from oxsecurity/megalinter/flavors/c_cpp's releases.

v10.2.0

What's Changed

• Core

  • Outside CI, PARALLEL_PROCESS_NUMBER now defaults to the number of cores minus one, so your machine stays responsive while MegaLinter runs. CI runs still use every core, and setting the variable still overrides the default (#9216)

• Linters enhancements

  • GROOVY_NPM_GROOVY_LINT upgraded to npm-groovy-lint v19: up to 18 times faster, and its default recommended preset now reports likely mistakes only (no style or layout rules) (#9411)
    • To get style and layout findings back, set "extends": "advanced" (or "all") in your .groovylintrc.json, see the migration guide
  • CLOJURE_CLJ_KONDO now lints all your Clojure files in a single clj-kondo run, with the new default list_of_files lint mode (#9029)
    • Cross-namespace checks, such as calls with a wrong number of arguments to a function defined in another file, are now reported without a clj-kondo cache
    • The console log and reports now show clj-kondo's warnings count, and its errors count when errors are found, instead of a single error for any failing run
    • clj-kondo now runs with --cache false: it no longer writes into your repository's .clj-kondo/.cache folder during the run, and no longer reads a cache built beforehand. To use such a cache, for example one built with --dependencies, set CLOJURE_CLJ_KONDO_COMMAND_REMOVE_ARGUMENTS: ["--cache", "false"]
    • To lint each file separately as before, set CLOJURE_CLJ_KONDO_CLI_LINT_MODE: file

• Fixes

  • With SARIF_REPORTER: true, findings the linter marks as suppressed in its SARIF output (for example # nosemgrep) no longer count as errors or warnings, and no longer appear in the console log, text reports and PR/MR comments. The SARIF reports still contain them. Fixes #9373
  • Improved security: R_LINTR, POWERSHELL_POWERSHELL, POWERSHELL_POWERSHELL_FORMATTER and ARM_ARM_TTK now handle file names containing quotes or special characters safely (#9404)
    • Files whose name contains control characters (such as a line break) are now skipped by these linters, with a warning in the log
  • EXTENDS now sends GITHUB_TOKEN only to https://raw.githubusercontent.com, to read configs in private repositories. A URL that merely starts with that text no longer receives it. See GHSA-rq55-6pj8-6v8v
    • Only extend from URLs hosted on an account or server owned by your organization, see Configuration
  • SPELL_LYCHEE now applies the .lycheeignore rules MegaLinter finds outside the repository root (for example in .github/linters with LINTER_RULES_PATH). Fixes #9281
  • Custom flavors including trivy no longer fail to build when the trivy vulnerability database mirror mirror.gcr.io is unavailable. Fixes #9254
    • The database download now tries mirror.gcr.io, ghcr.io and public.ecr.aws in turn, and waits between retries
    • Choose other mirrors with the new TRIVY_DB_REPOSITORY variable of the custom flavor builder workflow, see Custom flavors
    • A failed image build now fails the build step of the action, instead of a later No such object error when pushing the image
  • Go linters such as GO_GOLANGCI_LINT now work when MegaLinter runs as a non-root user (MEGALINTER_UID / MEGALINTER_GID): Go module and build caches go to the user's home folder, unless you set GOMODCACHE / GOCACHE yourself. Fixes #9280
  • A linter stopped by a signal (negative return code, such as an out-of-memory kill) now fails in file lint mode instead of reporting SUCCESS with 0 errors, and a PRE_COMMANDS / POST_COMMANDS entry with continue_if_failed: false stops the run. Fixes #9257
  • GitLab and Git environment variables such as GIT_STRATEGY no longer trigger a false removed-linter warning. Removed MegaLinter options and linter selections still warn. Fixes #9024
  • Pull request runs in private repositories no longer crash with a git traceback when the checkout does not persist credentials: MegaLinter warns, explains how to enable the git diff mode (persist-credentials: true or GIT_AUTHORIZATION_BEARER) and lints the whole codebase. Fixes #9104
  • FAIL_IF_UPDATED_SOURCES is now reliable. Fixes #9103
    • A warning is shown when its value is neither true nor false (for example an empty CI variable), and the console log tells whether the option is active
    • The failure reason, naming the linters that updated sources, is shown even when other linters failed too
    • It takes precedence over DISABLE_ERRORS: true: the exit code is 1, as the summary says
    • Sources updated by project lint mode linters and by POST_COMMANDS now fail the run too, and set the has_updated_sources output
  • The Email reporter no longer sends a mail for a successful run without updated sources unless EMAIL_REPORTER_SEND_SUCCESS is true, and the File.io reporter skips such runs when FILEIO_REPORTER_SEND_SUCCESS is true, as documented (#9219)
  • CLOJURE_CLJ_KONDO now really forwards EXCLUDED_DIRECTORIES and ADDITIONAL_EXCLUDED_DIRECTORIES in project lint mode: they were never applied before, so files in folders like node_modules or .wireit could be reported (#9029)
    • The directories are passed as a merged :output {:exclude-files [...]} inline configuration, so your own :output :exclude-files patterns in .clj-kondo/config.edn are kept
    • Disable the forwarding with CLOJURE_CLJ_KONDO_FORWARD_EXCLUDED_DIRECTORIES: false
  • The .mega-linter.yml JSON Schema is no longer rejected by strict JSON Schema validators with Invalid anchor value: the invalid $id values are removed from the configuration and descriptor schemas. Fixes #9177
  • Project lint mode no longer overrides the paths defined in the linters' own configuration: since v10, folders such as vendor/ were analyzed again by linters like phpcs, phpstan or editorconfig-checker, making runs slow and noisy. Fixes #8955
    • Linters that analyze the current folder by default are no longer passed .: eslint, biome, standard, ruff, ruff format, flake8, rubocop, phplint, jscpd, gherkin-lint, dart analyze, cljstyle and editorconfig-checker (which honours .gitignore again)
    • Linters requiring a path receive . only when their configuration does not define the paths to analyze: phpcs (<file>), phpstan (paths), psalm (<projectFiles>), php-cs-fixer (Finder in()), pylint and mypy (files), pyright (include), cfn-lint (templates), checkov (directory) and cspell (files)
    • The <LINTER_KEY>_COMMAND_REMOVE_ARGUMENTS: "." workaround is no longer needed
  • With IGNORE_GITIGNORED_FILES: true (default), the directories ignored by git are now forwarded to project lint mode linters with EXCLUDED_DIRECTORIES: a gitignored vendor/ or build/ folder is no longer analyzed by phpcs, trivy, checkov... (#9199)
    • A gitignored directory sharing its name with a tracked one (ex: /lib/ build output and src/lib sources) is only sent to the linters receiving exact paths, so your tracked sources stay analyzed
    • Disable it with the new FORWARD_GITIGNORED_DIRECTORIES: false variable
  • Your own exclusions are kept when MegaLinter forwards EXCLUDED_DIRECTORIES to project lint mode linters: the forwarded directories used to replace the exclusions defined in the linter's own configuration, so folders you left out were analyzed again. Fixes #8955
    • Exclusions from your config file are now kept for phplint (exclude), pylint (ignore), black (extend-exclude), flake8 (extend-exclude), isort (extend_skip), bandit (.bandit exclude), nbqa (exclude), djlint (extend_exclude), robocop (exclude), npm-groovy-lint (ignorepattern), rumdl (exclude) and jsonlint (patterns)

... (truncated)

Changelog

Sourced from oxsecurity/megalinter/flavors/c_cpp's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased] (beta, main branch content)

Note: Can be used with oxsecurity/megalinter@beta in your GitHub Action mega-linter.yml file, or with oxsecurity/megalinter:beta docker image

• Breaking changes

• Core

• New linters

• Disabled linters

• Re-enabled linters

• Deprecated linters

• Removed linters

• Media

• Linters enhancements

• Fixes

• Reporters

• Flavors

• Doc

• mega-linter-runner

• Agent Skills

• Dev

• CI

• Linter versions upgrades (N)

[v10.2.0] - 2026-10-31

• Core

... (truncated)

Commits

• f2fe8c1 Release MegaLinter v10.2.0
• 1a92b0e [automation] Auto-update linters version, help and documentation (#9421)
• 4cc4e24 [automation] Auto-update linters version, help and documentation (#9414)
• dfe4441 chore(deps): update dependency @​biomejs/biome to v2.6.3 (#9413)
• 28218ca Build(deps): Bump docker/login-action from 4.6.0 to 4.7.0 (#9418)
• 9c753cf Build(deps): Bump stefanzweifel/git-auto-commit-action from 7.2.0 to 7.2.1 (#...
• e0b0528 Build(deps): Bump actions/setup-python from 7.0.0 to 7.1.0 (#9420)
• d91114b [automation] Auto-update linters version, help and documentation (#9405)
• 5b15f9b chore(deps): update dependency phpstan/phpstan to v2.3.2 (#9412)
• e9a9378 chore(deps): upgrade npm-groovy-lint to v19.0.0 (#9411)
• Additional commits viewable in compare view

Updates github/codeql-action/upload-sarif from 4.39.1 to 4.39.3

Release notes

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

v4.39.3

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

v4.39.2

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

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.39.3 - 04 Nov 2026

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

4.39.1 - 21 Oct 2026

• Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

• Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205
• The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #4148
• Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #4206
• The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198

4.38.3 - 08 Oct 2026

• Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4188
• Update default CodeQL bundle version to 2.27.2. #4203
• Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #4184

4.38.2 - 24 Sept 2026

• Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

• The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #4146

4.38.0 - 09 Sept 2026

• On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #4124
• The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #4072
• Update default CodeQL bundle version to 2.27.0. #4129

... (truncated)

Commits

• 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
• 24393f8 Update changelog for v4.39.3
• 064910b Merge pull request #4297 from github/mbg/update-glob
• f532ac5 Update glob to 14.0.3
• 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
• cea289b Return different exit code when a language is not recognised
• 7287bb3 Remove exclude entry that's no longer needed
• 8eb7cdf Use normal .editorconfig pattern
• 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
• 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
• 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]

✅⚠️MegaLinter analysis: Success with warnings

Descriptor	Linter	Files	Fixed	Errors	Max errors	Warnings	Elapsed time
✅ ACTION	actionlint	7		0		0	0.72s
✅ CPP	clang-format	212	0	0		0	2.23s
✅ CPP	cppcheck	212		0		0	4.75s
✅ DOCKERFILE	hadolint	1		0		0	0.62s
✅ JSON	jsonlint	8		0		0	0.11s
✅ JSON	prettier	8	2	0		0	0.37s
✅ MARKDOWN	markdownlint	84	0	0		0	2.36s
✅ MARKDOWN	markdown-table-formatter	84	0	0		0	0.25s
⚠️ SPELL	lychee	132		2		0	3.47s
✅ YAML	prettier	12	0	0		0	0.59s
✅ YAML	yamllint	12		0		0	0.57s

Detailed Issues

⚠️ SPELL / lychee - 2 errors

[ERROR] failed to verify TLS certificate: invalid peer certificate: UnknownIssuer
📝 Summary
---------------------
🔍 Total..........379
🔗 Unique.........129
✅ Successful.....367
⏳ Timeouts.........0
🔀 Redirected.......5
👻 Excluded.........9
❓ Unknown..........0
🚫 Errors...........2
⛔ Unsupported......2

Errors in .github/workflows/static-analysis.yml
[403] https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-$ (at 37:21) | Rejected status code: 403 Forbidden

Errors in doc/kinematics/InverseKinematics.md
[ERROR] https://mathweb.ucsd.edu/~sbuss/ResearchWeb/ikmethods/iksurvey.pdf (at 125:169) | SSL certificate not trusted. Use --insecure if site is trusted

Hint: Followed 5 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

⚠️ Your configuration references items that have been removed from MegaLinter and are ignored: REPOSITORY_GITLEAKS, REPOSITORY_KICS. See Removed linters to find their replacements.

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@10.2.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,CPP_CPPCHECK,CPP_CLANG_FORMAT,DOCKERFILE_HADOLINT,JSON_JSONLINT,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,SPELL_LYCHEE,YAML_PRETTIER,YAML_YAMLLINT

Show us your support by starring ⭐ the repository