fix: looks like switching to new logger wasn't as straightforward

[iggy]

as I hoped

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	4		0	0	0.09s
✅ API	spectral	2		0	0	2.99s
✅ COPYPASTE	jscpd	yes		no	no	2.31s
✅ DOCKERFILE	hadolint	1		0	0	0.1s
✅ GO	golangci-lint	yes	yes	no	no	56.73s
✅ GO	revive	yes		no	no	1.94s
✅ MARKDOWN	markdownlint	2	0	0	0	0.87s
✅ MARKDOWN	markdown-table-formatter	2	0	0	0	0.31s
✅ REPOSITORY	checkov	yes		no	no	43.38s
✅ REPOSITORY	gitleaks	yes		no	no	0.43s
✅ REPOSITORY	git_diff	yes		no	no	0.0s
✅ REPOSITORY	grype	yes		no	no	65.78s
✅ REPOSITORY	secretlint	yes		no	no	0.83s
✅ REPOSITORY	syft	yes		no	no	3.37s
✅ REPOSITORY	trivy	yes		no	no	22.28s
✅ REPOSITORY	trivy-sbom	yes		no	no	3.75s
✅ REPOSITORY	trufflehog	yes		no	no	5.36s
✅ SPELL	lychee	14		0	0	0.07s
✅ YAML	prettier	12	0	0	0	0.93s
✅ YAML	v8r	12		0	0	15.43s
✅ YAML	yamllint	12		0	0	0.86s

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@9.4.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,API_SPECTRAL,COPYPASTE_JSCPD,DOCKERFILE_HADOLINT,GO_GOLANGCI_LINT,GO_REVIVE,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_GRYPE,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository