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

mega-linter-runner doesn't default to v6 for flavors #1596

Closed
karbassi opened this issue Jul 11, 2022 · 2 comments
Closed

mega-linter-runner doesn't default to v6 for flavors #1596

karbassi opened this issue Jul 11, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@karbassi
Copy link
Contributor

Describe the bug
After upgrading mega-linter-runner to v6, when running mega-linter-runner with the --flavor javascript flag, it defaults to v5.

To Reproduce
Steps to reproduce the behavior:

  1. npx mega-linter-runner --flavor javascript

Expected behavior
Should use v6 since it's stable.

Screenshots

$ npx mega-linter-runner --flavor javascript
#######################################################################
MEGA-LINTER HAS A NEW V6 VERSION. Please upgrade to it by:
- Running the command at the root of your repo (requires node.js): npx mega-linter-runner --upgrade
#######################################################################
Pulling docker image megalinter/megalinter-javascript:v5 ...
INFO: this operation can be long during the first use of mega-linter-runner
The next runs, it will be immediate (thanks to docker cache !)
v5: Pulling from megalinter/megalinter-javascript
...
...

Additional context

Running npx mega-linter-runner -r v6 -f javascript fixes the problem.

@karbassi karbassi added the bug Something isn't working label Jul 11, 2022
nvuillam added a commit that referenced this issue Jul 11, 2022
@nvuillam
Copy link
Member

nvuillam commented Jul 11, 2022

@karbassi Thank you for reporting !
I found the source of the error, it will be in a new v6 path tomorrow :)
Meanwhile you found the good workaround !

@nvuillam
Copy link
Member

@karbassi fixed in v6.0.3 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants