[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.16.3 → v0.16.5
• github.com/zizmorcore/zizmor-pre-commit: 451b56af716f9f0d0c2b816503a3fd0cf8b036fa → v1.30.0
• github.com/astral-sh/uv-pre-commit: 0.12.5 → 0.12.7

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[greptile-apps]

Greptile Summary

This automated dependency update bumps the ruff, zizmor, and uv pre-commit hook revisions.

• Updates ruff-pre-commit from v0.16.3 to v0.16.5.
• Updates zizmor-pre-commit from v1.29.0 to v1.30.0, while leaving its old version annotation unchanged.
• Updates uv-pre-commit from 0.12.5 to 0.12.7.

Confidence Score: 4/5

The PR appears safe to merge after correcting the non-blocking stale zizmor version annotation.

The upgraded hooks have no established compatibility failure in repository configuration, but the changed zizmor revision now conflicts with its adjacent human-readable version comment.

Files Needing Attention: .pre-commit-config.yaml

Important Files Changed

Filename	Overview
.pre-commit-config.yaml	The three hook revisions are updated, but the zizmor revision retains an inaccurate v1.29.0 inline annotation.

_{Reviews (1): Last reviewed commit: "[pre-commit.ci] pre-commit autoupdate" | Re-trigger Greptile}

[greptile-apps]

Stale zizmor version annotation

The revision now selects zizmor v1.30.0, but the adjacent comment still identifies it as v1.29.0, giving maintainers inaccurate dependency metadata during audits and future updates.

Suggested change

	rev: v1.30.0 # v1.29.0
	rev: v1.30.0 # v1.30.0