See release notes here -> https://github.com/oxsecurity/megalinter/releases/tag/v7.0.2

If you have any issue, please comment here :)

Click to see the video on Youtube, or check LinkedIn post

Impacting: Use of relative file paths to call linters

Now the linters are called with the relative file names, on contrary to the absolute file names used from the beginning of MegaLinter

Basically, for example we used to call eslint /tmp/lint/myfolder/myfile.js and now we call eslint myfolder/myfile.js

The only impacting issue seems to be with PRE_COMMANDS that install additonal npm dependencies.

• pre-commands are executed in /node-deps ONLY if they contain npm i or yarn add AND if the cwd is "root" (which is by default). Before it used to be in /node-deps undepending the cwd value
• If they do not work with cwd: root , it will probably work with cwd: workspace
• If you see such impact on your repo , please notify here in a comment :)

Known issues

Breaking changes

• composer is no longer in MegaLinter docker image. If you have PRE_COMMANDS using it, please install it previously with a PRE_COMMAND apk install composer (cf issue Composer no longer available for PRE_COMMANDS in v7.0.x #2702 )

Pending

• Tiny issue with upgrader , check that the report folder is megalinter-reports before committing :) (Waiting for NPM internal bug fix)

Released in 7.0.3

• Issue with some regex values in FILTER_REGEX_EXCLUDE found by @ruzickap in Some _FILTER_REGEX_EXCLUDE variables stopped working in v7.0.x #2697. Fixed in Manage v6 retrocompatiblity with FILTER_REGEX_INCLUDE and FILTER_REGEX_EXCLUDE expression #2698

Released in 7.0.4

• tflint not working in v7.x.x (cf tflint doesn't work in megalinter 7.0.x #2699). This is caused by GITHUB_TOKEN not sent anymore to tflint --init. This problem will be solved with PR Allow to define _UNSECURED_ENV_VARIABLES for specific linters #2703