Closed renovate[bot] closed 1 week ago
Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
---|---|---|---|---|---|
✅ API | spectral | 2 | 0 | 3.18s | |
✅ BASH | bash-exec | 5 | 0 | 0.02s | |
✅ BASH | shellcheck | 5 | 0 | 0.12s | |
✅ BASH | shfmt | 5 | 0 | 0 | 0.12s |
✅ COPYPASTE | jscpd | yes | no | 5.07s | |
✅ DOCKERFILE | hadolint | 129 | 0 | 17.6s | |
✅ JSON | jsonlint | 18 | 0 | 0.21s | |
✅ JSON | v8r | 20 | 0 | 28.42s | |
⚠️ MARKDOWN | markdownlint | 266 | 0 | 272 | 30.45s |
✅ MARKDOWN | markdown-table-formatter | 266 | 0 | 0 | 143.2s |
✅ OPENAPI | spectral | 2 | 0 | 3.04s | |
⚠️ PYTHON | bandit | 212 | 64 | 5.42s | |
✅ PYTHON | black | 212 | 0 | 0 | 4.96s |
✅ PYTHON | flake8 | 212 | 0 | 4.33s | |
✅ PYTHON | isort | 212 | 0 | 0 | 0.84s |
✅ PYTHON | mypy | 212 | 0 | 18.74s | |
✅ PYTHON | pylint | 212 | 0 | 17.32s | |
✅ PYTHON | ruff | 212 | 0 | 0 | 0.14s |
✅ REPOSITORY | checkov | yes | no | 43.68s | |
✅ REPOSITORY | git_diff | yes | no | 0.09s | |
⚠️ REPOSITORY | grype | yes | 1 | 24.02s | |
✅ REPOSITORY | secretlint | yes | no | 12.57s | |
✅ REPOSITORY | trivy | yes | no | 20.91s | |
✅ REPOSITORY | trivy-sbom | yes | no | 3.58s | |
⚠️ REPOSITORY | trufflehog | yes | 1 | 15.07s | |
✅ SPELL | cspell | 694 | 0 | 26.13s | |
⚠️ SPELL | lychee | 347 | 5 | 5.55s | |
✅ XML | xmllint | 3 | 0 | 0 | 0.09s |
✅ YAML | prettier | 161 | 0 | 0 | 4.95s |
✅ YAML | v8r | 102 | 0 | 196.03s | |
✅ YAML | yamllint | 162 | 0 | 2.4s |
See detailed report in MegaLinter reports
It seems there are multiple incompatibilities for now. Maybe we need to apply them one by one instead
@nvuillam It seems there are a couple of old dockerfiles of old tools (not kept updated). What should we do here? Clear the folders and see if they get regenerated?
@echoix former terraform folders can be removed as their linters have been moved in REPOSITORY descriptor, but the dockerfiles in /server are used for CodeTotal.io so must be maintained :)
And is there any tests that run for the server part, to know if the upgrades break some stuff or not?
@echoix no tests for server part (not good ^^)
But the server is based on MegaLinter base image so it's bad, but not that bad as it is used only for CodeTotal for now, and CodeTotal is not actively promoted
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.
So you're going to check (and test manually) that changing the image that runs the server still makes it work? I don't feel like I know what it should be like, and I don't feel comfortable on simply letting that much of a change untested.
So you're going to check (and test manually) that changing the image that runs the server still makes it work? I don't feel like I know what it should be like, and I don't feel comfortable on simply letting that much of a change untested.
The day CodeTotal / MegaLinter server will be used for production, I'll make tests, meanwhile... cross fingers, I have to choose my battles, can't take them all :D
This PR contains the following updates:
3.12.3
->3.12.4
3.11-alpine
->3.12-alpine
3.11.3-alpine3.17
->3.12.0-alpine3.17
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.