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 file by downgrading the gitleaks pre-commit hook from version v8.30.1 to v8.30.0. The change is minimal and straightforward, focusing only on the version pin of a single pre-commit tool. Overall, the PR is simple and does not introduce any code or functional changes beyond the configuration update.

---

Critical Issues

• None.
  The version change is valid and does not introduce any direct bugs or security problems.

Code Improvements

• Version Downgrade Reason
  • File: .pre-commit-config.yaml (line 14)
  • Issue: The PR downgrades gitleaks from v8.30.1 to v8.30.0 without explanation. Downgrading is unusual and could reintroduce previously fixed bugs or miss improvements.
  • Suggestion: Add a commit or PR description clarifying why the downgrade is necessary (e.g., compatibility issues, regressions in v8.30.1). This helps reviewers and future maintainers understand the rationale.

Best Practices

• Commit Message and PR Description
  • Issue: The PR description is auto-generated and does not explain the reason for the version change.
  • Suggestion: Enhance the PR description with context on why the downgrade is applied. For example:

    Downgrade gitleaks from v8.30.1 to v8.30.0 due to [reason], to avoid [issue].

• Testing the Pre-commit Hook
  • Issue: No indication if the updated pre-commit hooks were tested locally or on CI.
  • Suggestion: Confirm that the gitleaks hook runs successfully with the downgraded version and does not break existing workflows. Add a note or test logs if applicable.

---

No other meaningful code or configuration changes are present to review.