[automation] Auto-update linters version, help and documentation

[nvuillam]

[automation] Auto-update linters version, help and documentation

[github-actions[bot]]

🦙 MegaLinter status: ⚠️ WARNING

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ API	spectral	1		0	1.44s
⚠️ BASH	bash-exec	6		1	0.02s
✅ BASH	shellcheck	6		0	0.19s
✅ BASH	shfmt	6	0	0	0.82s
✅ COPYPASTE	jscpd	yes		no	3.36s
✅ DOCKERFILE	hadolint	128		0	18.55s
✅ JSON	jsonlint	20		0	0.2s
✅ JSON	v8r	22		0	31.68s
⚠️ MARKDOWN	markdownlint	266	0	297	33.24s
✅ MARKDOWN	markdown-table-formatter	266	0	0	159.65s
⚠️ PYTHON	bandit	212		66	4.12s
✅ PYTHON	black	212	0	0	6.83s
✅ PYTHON	flake8	212		0	2.68s
✅ PYTHON	isort	212	0	0	1.57s
✅ PYTHON	mypy	212		0	21.84s
✅ PYTHON	pylint	212		0	29.25s
✅ PYTHON	ruff	212	0	0	0.82s
✅ REPOSITORY	checkov	yes		no	35.95s
✅ REPOSITORY	git_diff	yes		no	0.79s
⚠️ REPOSITORY	grype	yes		24	15.87s
✅ REPOSITORY	secretlint	yes		no	15.61s
✅ REPOSITORY	trivy	yes		no	45.06s
✅ REPOSITORY	trivy-sbom	yes		no	0.46s
⚠️ REPOSITORY	trufflehog	yes		1	12.29s
✅ SPELL	cspell	713		0	12.19s
⚠️ SPELL	lychee	348		10	10.49s
✅ XML	xmllint	3	0	0	0.79s
✅ YAML	prettier	160	0	0	6.05s
✅ YAML	v8r	102		0	193.34s
✅ YAML	yamllint	161		0	2.93s

See detailed report in MegaLinter reports

_MegaLinter is graciously provided by _

[nvuillam]

@echoix do you have an idea about what's happening with gitpod ? it seems related to uv setup :/

[echoix]

@echoix do you have an idea about what's happening with gitpod ? it seems related to uv setup :/

Yep, rereading the error now I understand. Look at the second point of the uv's breaking changes for 0.5.0: https://github.com/astral-sh/uv/releases/tag/0.5.0

Use XDG (i.e. ~/.local/bin) instead of the Cargo home directory in the installer (# 8420)

Previously, uv's installer used $CARGO_HOME or ~/.cargo/bin for its target install directory. It's been a longstanding complaint that uv uses this directory, as there's no relationship to Cargo. Now, uv will be installed into $XDG_BIN_HOME, $XDG_DATA_HOME/../bin, or ~/.local/bin (in that order). Note that $UV_INSTALL_DIR can always be used to override the target directory. Upgrading with uv self update will not move uv to the new install directory.

[nvuillam]

@echoix do you have an idea about what's happening with gitpod ? it seems related to uv setup :/

Yep, rereading the error now I understand. Look at the second point of the uv's breaking changes for 0.5.0: https://github.com/astral-sh/uv/releases/tag/0.5.0

Use XDG (i.e. ~/.local/bin) instead of the Cargo home directory in the installer (# 8420) Previously, uv's installer used $CARGO_HOME or ~/.cargo/bin for its target install directory. It's been a longstanding complaint that uv uses this directory, as there's no relationship to Cargo. Now, uv will be installed into $XDG_BIN_HOME, $XDG_DATA_HOME/../bin, or ~/.local/bin (in that order). Note that $UV_INSTALL_DIR can always be used to override the target directory. Upgrading with uv self update will not move uv to the new install directory.

Thanks :)

I'll merge this PR to unlock other ones ^^

Do you think you can handle the gitpod error in another PR ?

[echoix]

Not tonight.

[nvuillam]

Not tonight.

Of course, this is open source, it's when you can :)