Giters

oxsecurity / megalinter

🦙 MegaLinter analyzes 50 languages, 22 formats, 21 tooling formats, excessive copy-pastes, spelling mistakes and security issues in your repository sources with a GitHub Action, other CI tools or locally.

Home Page:https://megalinter.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

MegaLinter V7 has been released :)

nvuillam opened this issue · comments

commented

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

V7 release

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 #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 #2697. Fixed in #2698

Released in 7.0.4

  • tflint not working in v7.x.x (cf #2699). This is caused by GITHUB_TOKEN not sent anymore to tflint --init. This problem will be solved with PR #2703
commented

Hi,
The newly introduced CLOJURE_CLJSTYLE linter has internal failures.
I'm getting this error for every Clojure file in my project:

 [cljstyle] project.clj - ERROR - 1 error(s)
  --Error detail:
  Unknown option: "-c"

I have to disable it to resolve the CI pipeline.

commented

@evg-tso it has been fixed in beta and will be released soon !

Meanwhile you can disable it, or use beta version

cf #2717

commented

@evg-tso released in 7.1.0 :)

commented

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.