chore(deps-dev): bump megalinter docker tag to v7 #608
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
forking-renovate
bot
added
the
dependencies
Kurt-von-Laven
force-pushed
the
renovate/megalinter
branch
2 times, most recently
from
b93dfeb
to
f83c3e8
Compare
MegaLinter recently added support for arrays to `*_CLI_EXECUTABLE` in v7.0.0. Leverage this feature to run the version of ESLint installed in our project via Yarn in lieu of the version of ESLint in the MegaLinter Docker image via npm. This avoids many complications that arise from ESLint being unable to access Yarn dependencies and allows us to stop running ESLint in project mode as a workaround. Reorder pre-commit hooks so that Yarn hooks precede MegaLinter hooks since `yarn install` must now be run before MegaLinter so that ESLint can run. Disable newly added linter ts-standard since we use Prettier, which is incompatible with StandardJS. Apply new Prettier v3 formatting. Configure newly added link checker Lychee to ignore email addresses to prevent false positives on GitHub Actions, which contain "@" symbols. Increase network request retry limit from the default of 3 to 4 to avoid false positives. | datasource | package | from | to | | ---------- | -------------------------------- | ------- | ------ | | docker | oxsecurity/megalinter-javascript | v6.22.2 | v7.2.1 |
Kurt-von-Laven
force-pushed
the
renovate/megalinter
branch
from
f83c3e8
to
aadcca5
Compare
Kurt-von-Laven
approved these changes
Aug 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MegaLinter recently added support for arrays to
*_CLI_EXECUTABLEin v7.0.0. Leverage this feature to run the version of ESLint installed in our project via Yarn in lieu of the version of ESLint in the MegaLinter Docker image via npm. This avoids many complications that arise from ESLint being unable to access Yarn dependencies and allows us to stop running ESLint in project mode as a workaround. Reorder pre-commit hooks so that Yarn hooks precede MegaLinter hooks sinceyarn installmust now be run before MegaLinter so that ESLint can run.Disable newly added linter ts-standard since we use Prettier, which is incompatible with StandardJS.
Apply new Prettier v3 formatting.
Configure newly added link checker Lychee to ignore email addresses to prevent false positives on GitHub Actions, which contain
@symbols. Increase network request retry limit from the default of 3 to 4 to avoid false positives.This PR contains the following updates:
v6.22.2->v7.2.1Release Notes
oxsecurity/megalinter (MegaLinter)
v7.2.1Compare Source
Fixes
--only-verifiedto avoid false positives in .git/configLinter versions upgrades
v7.2.0Compare Source
New linters
New flavor dotnetweb: dotnet flavor linters + Javascript & Typescript linters
Media
Core
Fixes
hadolintto use its default configuration file properly, by @KihyeokK in #2763--updatefor apk in Dockerfile by @PeterDaveHello in #2619Reporters
CI
Linter versions upgrades
v7.1.0Compare Source
Core
Linter enhancements & fixes
Linter versions upgrades
v7.0.4Compare Source
Core
linterkey_UNSECURED_ENV_VARIABLESfor specific linters to make them visible when necessary (ex: GITHUB_TOKEN for TERRAFORM_TFLINT)Documentation
Linter versions upgrades
v7.0.3Compare Source
Linter enhancements & fixes
true. Set tofalseto allowtflint --initto access your env vars.Core
Linter versions upgrades
v7.0.2Compare Source
v7.0.1Compare Source
v7.0.0Compare Source
To upgrade to MegaLinter v7, run
npx mega-linter-runner@latest --upgrade, comment here if you have any issue :)MAJOR Updates
New linters
Removed linters
Medias
Linter enhancements & fixes
VALIDATE_ALL_CODEBASEis set tofalse, by @DariuszPorowski #2504Core
Reporters
Warning Sign (U+26A0)instead of ◬White Up-Pointing Triangle with Dot (U+25EC), by @DoommiusDocumentation
Internal CI
/buildslash command to checkout the correct PR branch by @echoix in #2542Linter versions upgrades
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.