[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/gitleaks/gitleaks: v8.21.2 → v8.24.3
• https://github.com/google/osv-scanner/: v1.9.1 → v2.0.1
• github.com/pre-commit/pre-commit-hooks: v4.6.0 → v5.0.0

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[qodo-merge-pro]

CI Feedback 🧐

(Feedback updated until commit fce57c3)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: sonarcloud

Failed stage: [❌]

Failure summary: The action failed because the runner was shut down during the execution of the dev:lint task. The log shows that the runner received a shutdown signal at line 265, which can happen when the runner service is stopped or a manually started runner is canceled. The dev:lint task exited with a non-zero status (line 263) with "no exit status" because it was interrupted by the shutdown.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 248: ##[endgroup] 249: ##[group]Running mise install 250: [command]/home/runner/.local/share/mise/bin/mise install 251: �[2mmise�[0m all runtimes are installed 252: ##[endgroup] 253: ##[group]Run mise run dev:lint --no-fail 254: �[36;1mmise run dev:lint --no-fail�[0m 255: shell: /usr/bin/bash -e {0} 256: env: 257: MISE_EXPERIMENTAL: 1 258: MISE_LOG_LEVEL: info 259: MISE_TRUSTED_CONFIG_PATHS: /home/runner/work/sophrosyne/sophrosyne 260: MISE_YES: 1 261: ##[endgroup] 262: �[0m�[34m[dev:lint]�[0m �[1m$ ~/work/sophrosyne/sophrosyne/.mise/tasks/dev/lint --no-fail�[0m 263: �[0m�[34m[dev:lint]�[0m �[31mERROR�[0m ~/work/sophrosyne/sophrosyne/.mise/tasks/dev/lint exited with non-zero status: no exit status 264: �[0m�[34m[dev:lint]�[0m �[31mERROR�[0m task failed 265: ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled. 266: ##[error]The operation was canceled. 267: Cleaning up orphan processes