build: bump the patch-minor-action-updates group with 2 updates

[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.0.0 to 10.1.0

Release notes

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

v10.1.0

What's Changed

• Core

  • MegaLinter now prints a crash traceback when it is killed by a fatal signal (SIGSEGV, SIGBUS…), instead of exiting silently with no clue about what happened (#8779)
  • The LLM Advisor supports a new provider, OrcaRouter, an OpenAI-compatible AI gateway: set LLM_PROVIDER: orcarouter and ORCAROUTER_API_KEY in your environment to get fix suggestions routed through OrcaRouter (see the OrcaRouter provider page) (#8826)

• New linters

  • biome, one fast toolchain linting, formatting and sorting imports of JavaScript, TypeScript, JSX, TSX, JSON, CSS and GraphQL files, available as JAVASCRIPT_BIOME, TYPESCRIPT_BIOME, JSX_BIOME, TSX_BIOME, JSON_BIOME, CSS_BIOME and GRAPHQL_BIOME (#8706)
    • Activated only when a biome.json or biome.jsonc configuration file is found in the repository
    • Supports APPLY_FIXES (safe fixes with --write) and native SARIF output
    • EXCLUDED_DIRECTORIES are forwarded in project lint mode through a generated configuration extending the workspace one
  • ApexGuru, the AI-driven engine of Salesforce Code Analyzer, available as SALESFORCE_CODE_ANALYZER_APEXGURU (#8820)
    • Detects SOQL inefficiencies, critical anti-patterns and scalability hotspots in your .cls and .trigger files, with line-level highlights, severity ratings and suggested fixes
    • The analysis runs in a connected Salesforce org, not locally: store the auth url of the target org in a CI secret named SFDX_AUTH_URL, and MegaLinter logs in to that org before the scan
    • The scan is sent to that org explicitly, so a .sfdx/sfdx-config.json left at the root of the repository, usually naming a long gone scratch org, can not hijack it
    • Inactive by default: it activates only when SFDX_AUTH_URL is defined, so nothing changes for existing Salesforce projects
    • Requires ApexGuru to be enabled on the org: it needs Scale Center, and is available for Unlimited Edition production orgs, full copy sandboxes, Signature orgs and Scale Test customers
    • A run where the engine could not analyze anything is reported as an error rather than a silent success, together with the reason and how to fix it
    • Supports native SARIF output, like the other Code Analyzer engines
  • tofu fmt, the built-in formatter of OpenTofu (the MPL-2.0 licensed fork of Terraform), available as TERRAFORM_TOFU_FMT (#8729)
    • Analyzes .tofu files only, the OpenTofu specific extension, so it never doubles up with TERRAFORM_TERRAFORM_FMT which keeps .tf
    • To format your .tf files with OpenTofu instead, set TERRAFORM_TOFU_FMT_FILE_EXTENSIONS: [".tofu", ".tf", ".tfvars"] and DISABLE_LINTERS: [TERRAFORM_TERRAFORM_FMT]
    • Supports APPLY_FIXES to rewrite files in the canonical OpenTofu style
  • tofu validate, the built-in validator of OpenTofu, available as TERRAFORM_TOFU_VALIDATE (#8793)
    • Reports what formatters and rule-based linters can not see: unsupported or missing arguments, wrong attribute types, references to undeclared variables, locals or outputs, and broken module input contracts
    • Analyzes .tofu files only, like TERRAFORM_TOFU_FMT, leaving .tf free for a future terraform validate linter. To validate .tf files, set TERRAFORM_TOFU_VALIDATE_FILE_EXTENSIONS: [".tofu", ".tf"]
    • Validates one whole module per directory, so every .tf and .tofu file of a selected directory is parsed and can produce diagnostics
    • Every directory is initialized with tofu init -backend=false beforehand, so no state is read, no state lock is taken and no cloud credentials are needed
    • Set TERRAFORM_TOFU_VALIDATE_INIT_ARGUMENTS to change those initialization arguments, for example adding -lockfile=readonly to have an out-of-sync .terraform.lock.hcl reported as an error instead of being updated

• Disabled linters

  • COFFEE_COFFEELINT is disabled: CoffeeScript tooling is discontinued, and coffeelint can not receive EXCLUDED_DIRECTORIES in project lint mode (it has no exclusion option and reads .coffeelintignore only from its working directory). The linter will be removed in a future version (#8720)
  • GRAPHQL_GRAPHQL_SCHEMA_LINTER is disabled: graphql-schema-linter is unmaintained, with no release or commit since May 2022, and its peer dependency range pins graphql to ^15 || ^16, which held the whole GraphQL install back from graphql v17. Use GRAPHQL_BIOME to lint your GraphQL files. The linter will be removed in a future version (#8894)

• Re-enabled linters

  • spectral is back as API_SPECTRAL, together with the API descriptor, to lint your OpenAPI, AsyncAPI and Arazzo specifications (#8717)
    • It was removed in v10.0.0 because it crashed at startup on every run: the cause has been found and fixed
    • Nothing to change in your configuration: API_SPECTRAL works again in ENABLE_LINTERS / DISABLE_LINTERS, and the default ruleset file is still .spectral.yaml

• Linters enhancements

  • TERRAFORM_TFLINT now documents the tflint native GITHUB_TOKEN_github_com variable to authenticate plugin downloads on github.com, which is the recommended way to fix tflint --init failures when your GITHUB_TOKEN targets a GitHub Enterprise instance (#8795)
    • Set your github.com token in GITHUB_TOKEN_github_com, then list it in TERRAFORM_TFLINT_UNSECURED_ENV_VARIABLES: tflint gives it priority over GITHUB_TOKEN, which other linters and reporters keep using
    • PAT_GITHUB_COM is deprecated: it still works and now logs a warning, and will be removed in a future major release
  • CLOJURE_CLJSTYLE now forwards EXCLUDED_DIRECTORIES through its native repeatable --ignore argument, instead of a temporary .cljstyle written in your repository. Exclusions are now also applied when your repository already has a .cljstyle config, whose own ignore patterns are preserved (#8720)
  • SQL_SQLFLUFF does not receive EXCLUDED_DIRECTORIES in project lint mode anymore: sqlfluff reads path exclusions only from a .sqlfluffignore, .sqlfluff or pyproject.toml located inside the analyzed sources, where MegaLinter used to write a temporary file. List the directories to skip in your own .sqlfluffignore, or keep the default list_of_files lint mode where MegaLinter filters the files itself (#8720)
  • SARIF output is now available for 13 more linters: zizmor, bicep_linter, cppcheck, clj-kondo, roslynator, htmlhint, protolint, sqlfluff, swiftlint, osv-scanner, trufflehog, jscpd and lintr. Enable it the same way as any other SARIF-capable linter, with SARIF_REPORTER: true (optionally scoped with SARIF_REPORTER_LINTERS) (#8715)
    • The 4 Salesforce Code Analyzer engines (SALESFORCE_CODE_ANALYZER_APEX, _AURA, _LWC, _FLOW) also gained SARIF output: their report switches from CSV to SARIF automatically when SARIF reporting is requested
    • csharp_roslynator is bumped from 0.12.0 to 0.13.0, the first release including its SARIF output support

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

  • ApexGuru rate limits no longer fail CI test jobs: when Salesforce's ApexGuru service answers 429 Too Many Requests, the SALESFORCE_CODE_ANALYZER_APEXGURU success, failure and SARIF tests are skipped instead of failed
    • Only in CI (utils.is_ci()): local test runs still fail, so a real regression stays visible
    • Per-linter test jobs (deploy-DEV-linters.yml, deploy-BETA-linters.yml) now pass GITHUB_ACTIONS to the test container

• Linter versions upgrades (N)

... (truncated)

Commits

• 9949bad Release MegaLinter v10.1.0
• 4270990 fix release workflow
• 4d8bf14 [automation] Auto-update linters version, help and documentation (#8902)
• 98bcce2 fix(ci): install zensical in the auto-update linters container (#8901)
• b63dee7 fix(deps): update langchain (minor) (#8878)
• 4d17aee fix(renovate-rebase): force UTF-8 console output in tick_dashboard (#8900)
• b034be4 Disable the unmaintained graphql-schema-linter (#8894)
• e00d096 chore(deps): update dependency snakemake to v9.26.1 (#8897)
• 9591933 chore(deps): update dependency langsmith to v0.11.2 (#8896)
• e87989e chore(deps): update dependency golangci/golangci-lint to v2.13.2 (#8895)
• Additional commits viewable in compare view

Updates github/codeql-action/upload-sarif from 4.37.9 to 4.38.0

Release notes

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

v4.38.0

• 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

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

4.37.9 - 26 Aug 2026

• Update default CodeQL bundle version to 2.26.4. #4106

4.37.8 - 21 Aug 2026

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

... (truncated)

Commits

• b96794f Merge pull request #4131 from github/update-v4.38.0-7e08580a9
• 02d5093 Update changelog for v4.38.0
• 7e08580 Merge pull request #4130 from github/henrymercer/workflow-runner-sizing
• bfcc52b Run slow macOS checks on larger runners
• 8c251e7 Merge pull request #4129 from github/update-bundle/codeql-bundle-v2.27.0
• 0b7ca40 Add changelog note
• 40484b3 Update default bundle to codeql-bundle-v2.27.0
• 977e6ce Merge pull request #4124 from github/henrymercer/toolcache-bundle-cleanup
• 40a6b38 Address toolcache cleanup review feedback
• deece8f Apply suggestion from @​henrymercer
• 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.51s
✅ CPP	clang-format	30	6	0		0	0.96s
✅ CPP	cppcheck	30		0		0	1.47s
✅ DOCKERFILE	hadolint	1		0		0	0.68s
✅ JSON	jsonlint	8		0		0	0.09s
✅ JSON	prettier	8	3	0		0	0.38s
⚠️ MARKDOWN	markdownlint	101	0	138		0	2.13s
✅ MARKDOWN	markdown-table-formatter	101	4	0		0	0.21s
⚠️ SPELL	lychee	132		14		0	2.24s
✅ YAML	prettier	12	0	0		0	0.54s
✅ YAML	yamllint	12		0		0	0.69s

Detailed Issues

⚠️ SPELL / lychee - 14 errors

[ERROR] failed to verify TLS certificate: invalid peer certificate: UnknownIssuer
📝 Summary
---------------------
🔍 Total...........83
🔗 Unique..........42
✅ Successful......59
⏳ Timeouts.........0
🔀 Redirected.......3
👻 Excluded.........9
❓ Unknown..........0
🚫 Errors..........14
⛔ Unsupported.....14

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/dynamics/ArticulatedBodyAlgorithm.md
[ERROR] file://doc/solvers/GaussianElimination.md (at 91:3) | File not found. Check if file exists and path is correct

Errors in doc/dynamics/EulerLagrange.md
[ERROR] file://doc/controllers/Lqr.md (at 136:23) | File not found. Check if file exists and path is correct
[ERROR] file://doc/solvers/DiscreteAlgebraicRiccatiEquation.md (at 138:13) | File not found. Check if file exists and path is correct
[ERROR] file://doc/solvers/GaussianElimination.md (at 135:29) | File not found. Check if file exists and path is correct

Errors in doc/dynamics/NewtonEuler.md
[ERROR] file://doc/solvers/GaussianElimination.md (at 131:29) | File not found. Check if file exists and path is correct

Errors in doc/dynamics/RecursiveNewtonEuler.md
[ERROR] file://doc/solvers/GaussianElimination.md (at 134:29) | File not found. Check if file exists and path is correct

Errors in doc/kinematics/ForwardKinematics.md
[ERROR] file://doc/math/Geometry3D.md (at 66:71) | File not found. Check if file exists and path is correct

Errors in doc/kinematics/InverseKinematics.md
[ERROR] file://doc/solvers/GaussianElimination.md (at 114:3) | File not found. Check if file exists and path is correct
[ERROR] https://mathweb.ucsd.edu/~sbuss/ResearchWeb/ikmethods/iksurvey.pdf (at 119:169) | SSL certificate not trusted. Use --insecure if site is trusted

Errors in README.md
[ERROR] file:///releases/latest (at 46:14) | File not found. Check if file exists and path is correct

Errors in ROADMAP.md
[ERROR] file://numerical/controllers/implementations/Mpc.hpp (at 162:25) | File not found. Check if file exists and path is correct
[ERROR] file://numerical/math/Geometry3D.hpp (at 82:25) | File not found. Check if file exists and path is correct

Errors in roadmap/README.md
[ERROR] file://roadmap/filters/passive/ExponentialMovingAverage/implementation.md (at 24:1) | File not found. Check if file exists and path is correct

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

⚠️ MARKDOWN / markdownlint - 138 errors

leTensionDistribution/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/CableTensionDistribution/implementation.md:18 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/CableTensionDistribution/implementation.md:28 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/CableTensionDistribution/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/CableTensionDistribution/tests.md:20 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ComputedTorqueControl/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ComputedTorqueControl/implementation.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ComputedTorqueControl/implementation.md:29 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ComputedTorqueControl/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ComputedTorqueControl/tests.md:18 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/HybridPositionForceControl/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/HybridPositionForceControl/implementation.md:21 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/HybridPositionForceControl/implementation.md:35 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/HybridPositionForceControl/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/HybridPositionForceControl/tests.md:24 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ImpedanceControl/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ImpedanceControl/implementation.md:19 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ImpedanceControl/implementation.md:32 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ImpedanceControl/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/ImpedanceControl/tests.md:21 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/OperationalSpaceControl/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/OperationalSpaceControl/implementation.md:19 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/OperationalSpaceControl/implementation.md:31 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/OperationalSpaceControl/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/OperationalSpaceControl/tests.md:19 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/PdGravityCompensation/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/PdGravityCompensation/implementation.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/PdGravityCompensation/implementation.md:29 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/PdGravityCompensation/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/PdGravityCompensation/tests.md:19 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/SlotineLiAdaptiveControl/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/SlotineLiAdaptiveControl/implementation.md:20 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/SlotineLiAdaptiveControl/implementation.md:35 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/SlotineLiAdaptiveControl/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/controllers/manipulator/SlotineLiAdaptiveControl/tests.md:22 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/FrictionCompensation/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/FrictionCompensation/implementation.md:24 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/FrictionCompensation/implementation.md:36 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/FrictionCompensation/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/FrictionCompensation/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/GenericJointLink/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/GenericJointLink/implementation.md:22 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/GenericJointLink/implementation.md:36 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/GenericJointLink/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/dynamics/GenericJointLink/tests.md:19 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/AnalyticalIkPieper/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/AnalyticalIkPieper/implementation.md:20 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/AnalyticalIkPieper/implementation.md:27 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/AnalyticalIkPieper/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/AnalyticalIkPieper/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ContinuumKinematics/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ContinuumKinematics/implementation.md:21 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ContinuumKinematics/implementation.md:30 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ContinuumKinematics/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ContinuumKinematics/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/DenavitHartenberg/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/DenavitHartenberg/implementation.md:26 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/DenavitHartenberg/implementation.md:35 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/DenavitHartenberg/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/DenavitHartenberg/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ManipulabilityIndex/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ManipulabilityIndex/implementation.md:16 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ManipulabilityIndex/implementation.md:26 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ManipulabilityIndex/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ManipulabilityIndex/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/MobileManipulatorKinematics/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/MobileManipulatorKinematics/implementation.md:21 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/MobileManipulatorKinematics/implementation.md:30 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/MobileManipulatorKinematics/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/MobileManipulatorKinematics/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ParallelManipulatorKinematics/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ParallelManipulatorKinematics/implementation.md:26 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ParallelManipulatorKinematics/implementation.md:35 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ParallelManipulatorKinematics/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ParallelManipulatorKinematics/tests.md:16 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/PoseInverseKinematics/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/PoseInverseKinematics/implementation.md:30 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/PoseInverseKinematics/implementation.md:38 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/PoseInverseKinematics/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/PoseInverseKinematics/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ProductOfExponentials/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ProductOfExponentials/implementation.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ProductOfExponentials/implementation.md:25 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ProductOfExponentials/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/ProductOfExponentials/tests.md:18 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/RedundancyResolution/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/RedundancyResolution/implementation.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/RedundancyResolution/implementation.md:27 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/RedundancyResolution/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/RedundancyResolution/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/SpatialJacobian/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/SpatialJacobian/implementation.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/SpatialJacobian/implementation.md:26 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/SpatialJacobian/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/kinematics/SpatialJacobian/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/README.md:11 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/README.md:32:96 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
roadmap/README.md:33:96 error MD060/table-column-style Table column style [Table pipe does not align with header for style "aligned"]
roadmap/trajectory/CartesianSlerpInterpolation/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/CartesianSlerpInterpolation/implementation.md:23 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/CartesianSlerpInterpolation/implementation.md:32 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/CartesianSlerpInterpolation/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/CartesianSlerpInterpolation/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/PolynomialTrajectory/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/PolynomialTrajectory/implementation.md:27 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/PolynomialTrajectory/implementation.md:36 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/PolynomialTrajectory/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/PolynomialTrajectory/tests.md:16 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/SCurveProfile/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/SCurveProfile/implementation.md:26 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/SCurveProfile/implementation.md:35 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/SCurveProfile/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/SCurveProfile/tests.md:16 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TimeOptimalPathParameterization/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TimeOptimalPathParameterization/implementation.md:28 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TimeOptimalPathParameterization/implementation.md:37 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TimeOptimalPathParameterization/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TimeOptimalPathParameterization/tests.md:17 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TrapezoidalProfile/implementation.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TrapezoidalProfile/implementation.md:26 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TrapezoidalProfile/implementation.md:35 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TrapezoidalProfile/tests.md:7 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
roadmap/trajectory/TrapezoidalProfile/tests.md:16 error MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]

(Truncated to last 20000 characters out of 22405)

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.1.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

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.