chore: pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/gitleaks/gitleaks: v8.30.1 → v8.30.0

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign wuhuizuo for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Summary
This PR updates the .pre-commit-config.yaml to downgrade the gitleaks hook from version v8.30.1 to v8.30.0. The change is minimal and focused solely on the pre-commit configuration. The approach is straightforward, but the version downgrade is unusual and may need validation. Overall, the PR quality is fine but the rationale behind the version change should be clarified.

---

Critical Issues

• Potential unintended downgrade
  • File: .pre-commit-config.yaml (line 14)
  • Issue: The PR changes the gitleaks version from v8.30.1 to v8.30.0, effectively downgrading it. Usually, updates move forward to patch bugs or improve features. Downgrading may reintroduce fixed bugs or remove improvements.
  • Suggestion: Confirm and document why the downgrade is necessary. If it was unintentional, revert to the latest stable version (v8.30.1). Alternatively, include a note in the PR description explaining the reason (e.g., compatibility issues, regressions in v8.30.1).

---

Best Practices

• PR Description Clarity
  • File: PR description and .pre-commit-config.yaml
  • Issue: The PR description does not explain why the version is being downgraded, which can confuse reviewers and maintainers.
  • Suggestion: Add a brief explanation in the PR description about the downgrade rationale, e.g.,

    Downgrade gitleaks from v8.30.1 to v8.30.0 due to [specific issue or incompatibility].

No other changes are present, so no further feedback applies here.