Skip to content
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

Closed
nvuillam opened this issue May 27, 2023 · 4 comments
Closed

MegaLinter V7 has been released :) #2692

nvuillam opened this issue May 27, 2023 · 4 comments
Labels
O: stale 🤖 This issue or pull request is stale, it will be closed if there is no activity

Comments

@nvuillam
Copy link
Member

nvuillam commented May 27, 2023

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

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

Released in 7.0.4

@nvuillam nvuillam changed the title [WIP] MegaLinter V7 MegaLinter V7 has been released :) May 27, 2023
@nvuillam nvuillam pinned this issue May 27, 2023
@oxsecurity oxsecurity deleted a comment from Kurt-von-Laven May 28, 2023
@oxsecurity oxsecurity deleted a comment from Kurt-von-Laven May 28, 2023
@evg-tso
Copy link

evg-tso commented Jun 5, 2023

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.

@nvuillam
Copy link
Member Author

nvuillam commented Jun 5, 2023

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

Meanwhile you can disable it, or use beta version

cf #2717

@nvuillam
Copy link
Member Author

@evg-tso released in 7.1.0 :)

@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot added the O: stale 🤖 This issue or pull request is stale, it will be closed if there is no activity label Jul 12, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2023
@nvuillam nvuillam unpinned this issue May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O: stale 🤖 This issue or pull request is stale, it will be closed if there is no activity
Projects
None yet
Development

No branches or pull requests

3 participants
@evg-tso @nvuillam and others