Update pre-commit hooks

[yu-iskw]

PR Type

Enhancement

---

Description

• Update actionlint from v1.7.8 to v1.7.9

• Update pylint from v4.0.0 to v4.0.3

• Update ruff from v0.14.0 to v0.14.6

---

Diagram Walkthrough

flowchart LR
  A["Pre-commit Config"] -->|actionlint| B["v1.7.9"]
  A -->|pylint| C["v4.0.3"]
  A -->|ruff| D["v0.14.6"]

Loading

File Walkthrough

	Relevant files
Dependencies	.pre-commit-config.yaml Bump pre-commit hook tool versions                                              .pre-commit-config.yaml Updated actionlint from v1.7.8 to v1.7.9 Updated pylint from v4.0.0 to v4.0.3 Updated ruff from v0.14.0 to v0.14.6 +3/-3

---

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• .pre-commit-config.yaml is excluded by !**/*.yaml

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-pre-commit-hooks-04

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Out of scope: The PR only updates tool versions in pre-commit configuration and adds no application code that could affect audit logging, so compliance cannot be assessed from this diff alone. Referred Code rev: v1.7.9 hooks: - id: actionlint # - repo: https://github.com/asottile/reorder_python_imports # rev: v3.10.0 # hooks: # - id: reorder-python-imports - repo: https://github.com/asottile/setup-cfg-fmt rev: v3.1.0 hooks: - id: setup-cfg-fmt - repo: https://github.com/pycqa/isort rev: 7.0.0 hooks: - id: isort name: isort (python) - repo: https://github.com/pycqa/pylint rev: v4.0.3 hooks: - id: pylint exclude: (dbt_artifacts_parser/parsers/) ... (clipped 16 lines) Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: No code changes: Only version pins for pre-commit hooks were updated; there are no new identifiers or code constructs to evaluate for naming. Referred Code rev: v1.7.9 hooks: - id: actionlint # - repo: https://github.com/asottile/reorder_python_imports # rev: v3.10.0 # hooks: # - id: reorder-python-imports - repo: https://github.com/asottile/setup-cfg-fmt rev: v3.1.0 hooks: - id: setup-cfg-fmt - repo: https://github.com/pycqa/isort rev: 7.0.0 hooks: - id: isort name: isort (python) - repo: https://github.com/pycqa/pylint rev: v4.0.3 hooks: - id: pylint exclude: (dbt_artifacts_parser/parsers/) ... (clipped 16 lines) Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No error paths: The diff only changes pre-commit hook versions and introduces no runtime error handling logic to assess. Referred Code rev: v1.7.9 hooks: - id: actionlint # - repo: https://github.com/asottile/reorder_python_imports # rev: v3.10.0 # hooks: # - id: reorder-python-imports - repo: https://github.com/asottile/setup-cfg-fmt rev: v3.1.0 hooks: - id: setup-cfg-fmt - repo: https://github.com/pycqa/isort rev: 7.0.0 hooks: - id: isort name: isort (python) - repo: https://github.com/pycqa/pylint rev: v4.0.3 hooks: - id: pylint exclude: (dbt_artifacts_parser/parsers/) ... (clipped 16 lines) Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: No user errors: There are no user-facing error messages added or modified; only tool version updates are present. Referred Code rev: v1.7.9 hooks: - id: actionlint # - repo: https://github.com/asottile/reorder_python_imports # rev: v3.10.0 # hooks: # - id: reorder-python-imports - repo: https://github.com/asottile/setup-cfg-fmt rev: v3.1.0 hooks: - id: setup-cfg-fmt - repo: https://github.com/pycqa/isort rev: 7.0.0 hooks: - id: isort name: isort (python) - repo: https://github.com/pycqa/pylint rev: v4.0.3 hooks: - id: pylint exclude: (dbt_artifacts_parser/parsers/) ... (clipped 16 lines) Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: No logging changes: The PR does not add or modify application logging; only pre-commit tool versions were updated, so logging practices cannot be evaluated here. Referred Code rev: v1.7.9 hooks: - id: actionlint # - repo: https://github.com/asottile/reorder_python_imports # rev: v3.10.0 # hooks: # - id: reorder-python-imports - repo: https://github.com/asottile/setup-cfg-fmt rev: v3.1.0 hooks: - id: setup-cfg-fmt - repo: https://github.com/pycqa/isort rev: 7.0.0 hooks: - id: isort name: isort (python) - repo: https://github.com/pycqa/pylint rev: v4.0.3 hooks: - id: pylint exclude: (dbt_artifacts_parser/parsers/) ... (clipped 16 lines) Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: No input handling: No application input handling or data processing code was added; only pre-commit configuration version bumps are present, so security validation cannot be assessed. Referred Code rev: v1.7.9 hooks: - id: actionlint # - repo: https://github.com/asottile/reorder_python_imports # rev: v3.10.0 # hooks: # - id: reorder-python-imports - repo: https://github.com/asottile/setup-cfg-fmt rev: v3.1.0 hooks: - id: setup-cfg-fmt - repo: https://github.com/pycqa/isort rev: 7.0.0 hooks: - id: isort name: isort (python) - repo: https://github.com/pycqa/pylint rev: v4.0.3 hooks: - id: pylint exclude: (dbt_artifacts_parser/parsers/) ... (clipped 16 lines) Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.