[dependabot]

Bumps oxsecurity/megalinter from 10.1.0 to 10.2.0.

Release notes

Sourced from oxsecurity/megalinter'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's changelog.

[v10.2.0] - 2026-10-31

• 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)
    • The tools' own default exclusions are kept for ansible-lint, cspell, pylint and gherkin-lint
    • csharpier keeps honouring .gitignore, v8r your ignorePatternFiles, yamllint an ignore inherited through extends or an ignore-from-file, and StyLua the file patterns of .styluaignore and .gitignore (and .luau files are linted again)

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

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)