-
-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MegaLinter V7 has been released :) #2692
Comments
Hi,
I have to disable it to resolve the CI pipeline. |
@evg-tso released in 7.1.0 :) |
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
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 calleslint myfolder/myfile.js
The only impacting issue seems to be with PRE_COMMANDS that install additonal npm dependencies.
/node-deps
ONLY if they containnpm i
oryarn add
AND if the cwd is "root" (which is by default). Before it used to be in/node-deps
undepending the cwd valuecwd: root
, it will probably work withcwd: workspace
Known issues
Breaking changes
apk install composer
(cf issue Composer no longer available for PRE_COMMANDS in v7.0.x #2702 )Pending
Released in 7.0.3
Released in 7.0.4
tflint --init
. This problem will be solved with PR Allow to define _UNSECURED_ENV_VARIABLES for specific linters #2703The text was updated successfully, but these errors were encountered: